Cyber Resilience

CVE-2025-13632

Google Chrome ≤ 143.0.7499.40

Published
02 December 2025
Modified
04 December 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
EPSS Score 0.0023 14th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

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

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

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-13720Same product: Apple Macos
CVE-2026-6305Same product: Apple Macos
CVE-2026-6314Same product: Apple Macos
CVE-2025-11205Same product: Apple Macos
CVE-2025-13042Same product: Apple Macos
CVE-2025-9132Same product: Apple Macos
CVE-2026-7899Same product: Apple Macos
CVE-2026-10941Same product: Apple Macos
CVE-2026-3062Same product: Apple Macos
CVE-2026-11173Same product: Apple Macos

Affected Assets

google
chrome
≤ 143.0.7499.40 · ≤ 143.0.7499.40

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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing in development can detect unexpected sign-extension behavior through targeted test cases.

prevents

Secure development lifecycle includes practices that can catch sign-extension issues during design and review.

prevents

Application security requirements can mandate safe type handling and input validation to avoid sign-extension bugs.

prevents

Secure architecture principles encourage use of safe data types and explicit casting, reducing sign-extension risk.

prevents

Secure coding standards directly address integer handling and sign-extension pitfalls in source code.

References