Security Resilience

CVE-2026-87546

Google Chrome ≤ 153.0.8010.36

Published
09 September 2026
Modified
14 September 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.3
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:L/A:N
EPSS Score 0.0026 17th percentile
Risk Priority 36 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-87546 is a medium-severity Incorrect Type Conversion or Cast (CWE-704) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 17th 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

Incorrect type conversion or cast in Safebrowsing in Google Chrome on on Mac prior to 153.0.8010.36 allowed a remote attacker to bypass system access restrictions via a crafted file. (Chromium security severity: Low)

CWE(s)
CWE-704

Related Threats

CVEs Like This One

CVE-2026-11690Same product: Apple Macos
CVE-2026-9122Same product: Apple Macos
CVE-2026-17712Same product: Apple Macos
CVE-2024-11920Same product: Apple Macos
CVE-2026-13792Same product: Apple Macos
CVE-2026-13998Same product: Apple Macos
CVE-2026-17864Same product: Apple Macos
CVE-2026-12020Same product: Apple Macos
CVE-2026-17710Same product: Apple Macos
CVE-2026-17701Same product: Apple Macos

Affected Assets

google
chrome
≤ 153.0.8010.36

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds incorrect type conversions or casts.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate safe typing, casting rules, and compiler checks that stop the weakness from being introduced.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles can require type-safe design and casting practices that structurally avoid incorrect conversions.

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.

A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle includes type-safety reviews that reduce incorrect casts.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent any type-conversion defects from arising or being exploitable.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure architecture principles discourage unsafe type conversions in design.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid or detect incorrect type casts.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can uncover type-conversion defects before release.

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

References