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-126916 google chrome: Year 2038 problem, Y2K38, Y2038, Epochalypse
High (8.8) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Integer overflow in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to 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; 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-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
- 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-126916 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126916?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126916?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-126916 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-126916)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126916"><img src="https://cve.bz/cve/badge/CVE-2026-126916.svg" alt="CVE-2026-126916"></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-126916 |
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 rather than Critical because successful exploitation is confined within the application's renderer sandbox, preventing direct access to the underlying operating system without an accompanying sandbox escape. An unauthenticated remote attacker can trigger this flaw by convincing a user to navigate to malicious web content. In Red Hat Enterprise Linux workstation and desktop installations where Chromium is utilized, exploitation requires active user interaction, which prevents direct or automated network-based compromise.
Operational mitigation involves restricting exposure to untrusted web content and ensuring sandbox restrictions remain enforced:
1. Avoid visiting untrusted websites or following unverified links within the browser.
2. Ensure Chromium's built-in sandbox remains active and is never bypassed (do not launch the browser with flags that disable sandboxing).
Caveats:
These operational measures reduce the probability of encountering exploit vectors and restrict unauthorized execution to the isolated renderer process, but they do not eliminate the underlying defect when processing untrusted JavaScript.
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-126916.
Attack patterns (CAPEC)
- CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- Scored 8.8 high
Changes since this site first stored the record. The same for every record: /api/public/changes.