Security Resilience

CVE-2026-95370

Google Chrome ≤ 154.0.8037.57

Public PoC
Published
29 September 2026
Modified
01 October 2026
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 42 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-95370 is a medium-severity Improper Enforcement of Behavioral Workflow (CWE-841) vulnerability in Google Chrome. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 5th 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 IA-11 (Re-authentication) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Inappropriate implementation in NFC in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-79083Same product: Google Chrome
CVE-2026-113308Same product: Google Chrome
CVE-2026-113094Same product: Google Chrome
CVE-2026-95369Same product: Google Chrome
CVE-2026-17829Same product: Google Chrome
CVE-2026-10980Same product: Google Chrome
CVE-2026-17758Same product: Google Chrome
CVE-2026-14382Same product: Google Chrome
CVE-2026-14414Same product: Google Chrome
CVE-2026-17783Same 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 can require each successive workflow step to present the proper authorization context before proceeding.

Re-authentication requirements can be placed at critical workflow steps to ensure the actor has performed prior behaviors.

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 workflow bypasses but does not enforce them at runtime.

prevents

Secure coding practices can prevent missing workflow checks but do not define the control itself.

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-841, a class-level weakness, and none of its children carries one either.

References