Security Resilience

CVE-2026-87529

Google Chrome ≤ 153.0.8010.36

Published
09 September 2026
Modified
10 September 2026
Patch / advisory
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0050 42th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-87529 is a critical-severity Numeric Truncation Error (CWE-197) vulnerability in Google Chrome. Its CVSS base score is 9.6 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked at the 42th 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.

EU & UK References

Vulnerability Data

Numeric truncation error in Media in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-10999Same product: Google Chrome
CVE-2024-8636Same product: Google Chrome
CVE-2024-8638Same product: Google Chrome
CVE-2024-6772Same product: Google Chrome
CVE-2024-8198Same product: Google Chrome
CVE-2024-7534Same product: Google Chrome
CVE-2024-7022Same product: Google Chrome
CVE-2024-6990Same product: Google Chrome
CVE-2026-14420Same product: Google Chrome
CVE-2026-15114Same product: Google Chrome

Affected Assets

google
chrome
≤ 153.0.8010.36

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover truncation errors through static analysis, dynamic testing, or code review.

Documented development standards and tools can mandate use of safe arithmetic libraries or explicit checks against truncation.

Engineering principles can require safe type conversions and avoidance of narrowing casts that cause truncation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent truncation errors via reviews, static analysis, and safe type handling.

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

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Secure development lifecycle mandates practices that can catch numeric truncation during design and code review.

prevents

Secure coding standards directly prohibit unsafe narrowing conversions and truncation.

finds

Security testing can detect truncation bugs through static analysis and fuzzing.

References