CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVE-2026-126908 google chrome: Type Confusion
High (8.8) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Type confusion in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
- Published
- Modified
- Assigned by
- Chrome (CNA)
- NVD analysis
- Under analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126908 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126908?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126908?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126908 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126908)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126908"><img src="https://cve.bz/cve/badge/CVE-2026-126908.svg" alt="CVE-2026-126908"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.78 before 157.0.8103.78 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | chromium | no fix listed | DEBIAN-CVE-2026-126908 |
From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.
Red Hat
Red Hat rates this Important.
This vulnerability is rated as Important because remote attackers can achieve arbitrary code execution within the renderer sandbox by convincing a user to navigate to a malicious website, without requiring prior privileges. Although Chromium's multi-process sandbox restricts direct compromise of the underlying host operating system, executing arbitrary code inside the renderer breaks the confidentiality and integrity of the user's active session. On Red Hat Enterprise Linux, the browser is run interactively as a desktop client, requiring user interaction to encounter untrusted web content rather than exposing an unattended network service.
Operational mitigation involves restricting exposure to untrusted web content and ensuring renderer sandboxing protections remain enforced:
1. Operational controls:
Avoid visiting untrusted, suspicious, or unfamiliar websites, and do not follow untrusted links.
2. Enforce sandboxing:
Ensure that the browser sandbox is enabled. Do not launch the application with the `--no-sandbox` command-line option.
3. Restrict JavaScript execution:
In environments where untrusted web content must be inspected, disable JavaScript or restrict it to trusted domains via the browser configuration settings (Settings -> Privacy and security -> Site settings -> JavaScript). Alternatively, launch the browser with JavaScript disabled:
chromium-browser --disable-javascript
Caveat: Disabling JavaScript will severely impact functionality and render many modern web applications unusable.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-126908.
History
- Scored 8.8 high
Changes since this site first stored the record. The same for every record: /api/public/changes.