# CVE-2026-3910: Google Chromium V8 Improper Restriction of Operations Within the Bounds of a Memory Buffer

> Remote attackers can execute arbitrary code inside the sandbox via a crafted HTML page due to inappropriate V8 implementation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 13 Mar 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 14 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-3910, GHSA-69wh-543j-25h6, MINI-qc89-qgm6-59c6

## What is CVE-2026-3910?

CVE-2026-3910 is a high-severity code injection vulnerability in Google Chrome, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-3910?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2026-3910?

Upgrade to a fixed version. US federal agencies must fix it by 27 Mar 2026.

## Is CVE-2026-3910 being exploited?

Yes. Attackers have exploited CVE-2026-3910 in the wild since at least 13 Mar 2026.

Public exploit code:

- https://github.com/5o1z/CVE-2026-3910 (github_poc): https://github.com/5o1z/CVE-2026-3910

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3910 and fix it if it is affected.

What it is: CVE-2026-3910 is a high-severity code injection vulnerability in Google Chrome, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-3910 in the wild since at least 13 Mar 2026.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3910/ (Markdown: https://insights.sbomify.com/CVE-2026-3910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3910
- OSV: https://osv.dev/vulnerability/CVE-2026-3910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3910/
Summaries are generated and may contain mistakes; the official description above is the record.