CVE-2026-95316
Google Chrome ≤ 154.0.8037.57
Raw vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS 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-95316 is a low-severity Unchecked Return Value (CWE-252) vulnerability in Google Chrome. Its CVSS base score is 2.9 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-89166
Vulnerability Data
Unchecked return value in Performance in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially read memory via a local program. (Chromium security severity: Low)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Developer testing and code evaluation can discover instances where return values are ignored.
Requiring a documented development process and coding standards can mandate explicit checking of all function return values.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require checking and handling all function return values to detect error conditions.
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.
Security testing in development and acceptance can detect missing return-value checks.
Training developers in defensive programming and error-handling practices reduces instances of unchecked return values, but the practice is fallible and a different clause (e.g., A.8.28 secure coding, A.8.29 security testing) carries the stronger effect, matching the A.6.3 vs CWE-598 and A.8.28 vs CWE-79 anchors.
Secure coding explicitly requires checking return values to avoid CWE-252.
A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; unchecked return values are a regular implementation defect that secure coding and security testing would catch, but the clause's mechanism is contractual and the practices are fallible, matching the owner-graded `partial` on A.8.30 vs CWE-134.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw — and CWE-252 is a first-party code defect that surfaces as CVEs only when it appears in a third-party component; the disclosed share is a minority, capping the rung at `partial`.