Security Resilience

CVE-2026-95275

Google Chrome ≤ 154.0.8037.57

Public PoC
Published
29 September 2026
Modified
02 October 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score 0.0027 20th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-95275 is a medium-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Incorrect reference resolution in MediaStream in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to bypass web origin policy into a privileged page via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-95334Same product: Google Chrome
CVE-2026-106181Same product: Google Chrome
CVE-2026-113102Same product: Google Chrome
CVE-2026-113223Same product: Google Chrome
CVE-2026-87613Same product: Google Chrome
CVE-2026-113159Same product: Google Chrome
CVE-2026-119270Same product: Google Chrome
CVE-2026-78985Same product: Google Chrome
CVE-2026-87547Same product: Google Chrome
CVE-2026-121200Same product: Google Chrome

Affected Assets

google
chrome
≤ 154.0.8037.57

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Access enforcement applies authorization checks to the resolved resource, blocking access outside the intended sphere.

Information flow enforcement can constrain flows that result from an incorrectly resolved name or reference.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect incorrect name or reference resolution through fuzzing and negative test cases.

prevents

Secure-coding standards directly address canonicalization, input validation and safe name resolution, mitigating CWE-706.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-706, a class-level weakness, and none of its children carries one either.

References