cve.bz

CVE-2026-126910 google chrome: Type Confusion

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
Type confusion 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

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

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-126910](https://cve.bz/cve/badge/CVE-2026-126910.svg)](https://cve.bz/cve/CVE-2026-126910)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 157.0.8103.78 before 157.0.8103.78

Linux distributions

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

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 this flaw as an Important severity impact because it allows remote attackers to execute arbitrary code within the browser renderer process if a user is tricked into visiting a malicious webpage. In typical Red Hat Enterprise Linux desktop deployments, Chromium processes web content under standard user privileges, meaning exploitation requires direct interaction from a local user to open untrusted content. While the potential for remote execution elevates the risk above Moderate, the severity does not reach Critical because the compromised process remains confined within the multi-process browser sandbox, preventing direct access to host system resources without an additional sandbox escape.

Red Hat's mitigation

Operational controls can reduce the risk of exploitation:

1. Avoid visiting untrusted websites or following unverified links.

2. Ensure the browser's built-in security sandbox remains active and is not disabled.

3. Disable JavaScript execution in Chromium site settings to prevent triggering the vulnerable V8 engine.

Caveat: Disabling JavaScript will severely impact the usability and functionality of modern interactive web applications.

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

History

  1. Scored 8.8 high

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

References

Check your stackJSON