cve.bz

CVE-2026-126890 google chrome: Out-of-bounds Read

8.8 highEPSS 0.3%

High (8.8) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Out of bounds read in Media 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

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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-125 Out-of-bounds Read
Published
Modified
Assigned by
Chrome (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126890 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126890?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126890?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-126890 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

CVE-2026-126890

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:

[![CVE-2026-126890](https://cve.bz/cve/badge/CVE-2026-126890.svg)](https://cve.bz/cve/CVE-2026-126890)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126890"><img src="https://cve.bz/cve/badge/CVE-2026-126890.svg" alt="CVE-2026-126890"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 157.0.8103.78 before 157.0.8103.78

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14chromiumno fix listedDEBIAN-CVE-2026-126890

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's statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

Red Hat's mitigation

Advise users to avoid accessing untrusted websites, opening unverified links, or processing untrusted HTML media content. Ensure that Chromium's built-in multi-process sandbox remains active; do not launch the browser with sandbox-disabling options such as `--no-sandbox`.

On systems where desktop web browsing is not required (such as headless servers or environments where alternative browsers are standard), exposure can be eliminated by removing the optional browser package:

# dnf remove chromium-browser

Caveats: Removing the package removes the Chromium browser from the system and will disrupt local web browsing workflows and any dependent desktop applications. Ensure that administrative tools or user workflows do not depend on this package prior to removal.

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-126890.

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Scored 8.8 high
  2. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON