CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NCVE-2026-126896 google chrome: Missing Authorization
High (8.1) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Missing authorization in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 21st 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-862 Missing Authorization
- OWASP Top 10
- A01:2025 Broken Access Control
- 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-126896 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126896?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126896?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-126896 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-126896)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126896"><img src="https://cve.bz/cve/badge/CVE-2026-126896.svg" alt="CVE-2026-126896"></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-126896 |
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 successful exploitation allows a remote attacker to circumvent same-origin policy boundaries, potentially exposing or modifying sensitive session information across different web contexts. In standard Red Hat Enterprise Linux workstation deployments where Chromium is utilized, exploitation necessitates that a user actively visits a malicious or compromised web page. Despite the requirement for user interaction, the ability to breach domain isolation without requiring elevated privileges poses a substantial risk to user data confidentiality and integrity.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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-126896.
Attack patterns (CAPEC)
- CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- Scored 8.1 high
Changes since this site first stored the record. The same for every record: /api/public/changes.