cve.bz

CVE-2026-126862 google chrome: Improper Input Validation

7.7 highEPSS 0.08%

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

On this page
Improper input validation in Core in Google Chrome on on Android prior to 157.0.8103.78 allowed a local attacker to bypass web origin policy via a co-installed app. (Chromium security severity: High)

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.08% estimated probability of exploitation activity in the next 30 days; 0th 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-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
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-126862 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126862?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126862?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-126862 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-126862

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

HTML:

<a href="https://cve.bz/cve/CVE-2026-126862"><img src="https://cve.bz/cve/badge/CVE-2026-126862.svg" alt="CVE-2026-126862"></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-126862

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

This vulnerability is rated as Important because a failure in origin verification could enable an attacker to circumvent same-origin boundaries and compromise cross-site confidentiality and integrity without requiring user interaction. However, this flaw targets mobile application interaction models on the Android platform, requiring a locally co-installed program to trigger the defect. Because Red Hat Enterprise Linux desktop environments do not implement the Android application framework, standard deployments are not directly exposed to this attack vector.

Red Hat's mitigation

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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

History

  1. Scored 7.7 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