Security Resilience

CVE-2026-95366

Google Chrome ≤ 154.0.8037.57

Public PoC
Published
29 September 2026
Modified
01 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.0022 13th percentile
Risk Priority 50 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-95366 is a medium-severity Operation on a Resource after Expiration or Release (CWE-672) vulnerability in Google Chrome. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 13th 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-2 (Account Management) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Use of released resource in Core in Google Chrome prior to 154.0.8037.57 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-106345Same product: Google Chrome
CVE-2026-121256Same product: Google Chrome
CVE-2026-106310Same product: Google Chrome
CVE-2026-106339Same product: Google Chrome
CVE-2026-106320Same product: Google Chrome
CVE-2026-113216Same product: Google Chrome
CVE-2026-14415Same product: Google Chrome
CVE-2026-17898Same product: Google Chrome
CVE-2025-12907Same product: Google Chrome
CVE-2022-0609Same 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.

Account lifecycle management includes explicit revocation and disabling steps that stop subsequent operations on released accounts or identifiers.

Access enforcement applies current authorizations to every request, directly blocking operations once a resource has been revoked or released.

Identifier management requires deallocation and reuse controls that prevent continued use of released identifiers.

Authenticator management mandates revocation and replacement procedures that render expired credentials unusable.

Clearing or isolating shared resources after release reduces the chance that stale data can be operated on.

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 use-after-release but does not prevent it at runtime.

prevents

Secure-coding rules require checks that prevent operations on freed or expired objects.

blocks

Change-management processes can introduce or remove resource-lifetime controls.

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

References