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-126876 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 Skia 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; 27th 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
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126876 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126876?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126876?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-126876 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-126876)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126876"><img src="https://cve.bz/cve/badge/CVE-2026-126876.svg" alt="CVE-2026-126876"></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 |
Fix and patched versions
- Vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | chromium | no fix listed | DEBIAN-CVE-2026-126876 |
| Debian | 14 | libskia, chromium | no fix listed | DEBIAN-CVE-2026-126876 |
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.
Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
To reduce exposure to this vulnerability, apply operational controls and ensure sandboxing is maintained:
1. Avoid visiting untrusted websites or following untrusted links that could render malicious HTML and graphics content.
2. Ensure that Chromium's built-in multi-process sandbox remains enabled. Do not run the browser with sandbox-disabling options such as the `--no-sandbox` command-line flag.
3. If the browser is not required on the system, remove the package:
# dnf remove chromium-browser
Caveats: Restricting web browsing or removing the browser package will affect user workflows that depend on web access. Operational controls such as avoiding untrusted content do not eliminate risk from compromised trusted sites.
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-126876.
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
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.