CVE-2025-13632
Google Chrome ≤ 143.0.7499.40
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:LSummary
CVE-2025-13632 is a medium-severity Unexpected Sign Extension (CWE-194) vulnerability in Google Chrome. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 14th 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
- 🇪🇺 ENISA EUVD: EUVD-2025-200317
Vulnerability Data
Inappropriate implementation in DevTools in Google Chrome prior to 143.0.7499.41 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover sign-extension bugs through static analysis, fuzzing, or targeted unit tests.
Documented development standards and tools can mandate safe integer handling and prohibit dangerous casts that produce sign extension.
Secure engineering principles require safe type conversion and arithmetic handling that structurally avoids unintended sign extension.
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.
Secure SDLC practices with static analysis and code review directly prevent sign-extension flaws during development.
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.
Security testing in development can detect unexpected sign-extension behavior through targeted test cases.
Secure development lifecycle includes practices that can catch sign-extension issues during design and review.
Application security requirements can mandate safe type handling and input validation to avoid sign-extension bugs.
Secure architecture principles encourage use of safe data types and explicit casting, reducing sign-extension risk.
Secure coding standards directly address integer handling and sign-extension pitfalls in source code.