CVE-2025-10891
Google Chrome ≤ 140.0.7339.207
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-10891 is a high-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-10891 is an integer overflow vulnerability (CWE-472) in the V8 JavaScript and WebAssembly engine within Google Chrome versions prior to 140.0.7339.207. The flaw allows a remote attacker to potentially trigger heap corruption by processing a crafted HTML page, as reported with a Chromium security severity rating of High and a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
A remote attacker can exploit this vulnerability by convincing a user to visit a malicious website or interact with a specially crafted HTML page, requiring no privileges but relying on user interaction. Successful exploitation could lead to arbitrary code execution, including potential remote code execution with the renderer process privileges, enabling high-impact confidentiality, integrity, and availability violations such as data theft, sandbox escape precursors, or full compromise of the affected browser instance.
Mitigation is addressed in the Google Chrome Stable Channel update announced on the Chrome Releases blog (https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_23.html), which patches the issue in version 140.0.7339.207 and later. Additional details are available in the Chromium issue tracker (https://issues.chromium.org/issues/443765373). Security practitioners should prioritize updating affected Chrome installations and advise users to enable automatic updates.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-31015
Vulnerability Data
Integer overflow in V8 in Google Chrome prior to 140.0.7339.207 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (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
SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.
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 directly require server-side validation of all inputs instead of trusting client-supplied immutable parameters.
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.
Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.
Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.
Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.
Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.
Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.