Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-3914 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 at the 28th 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 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-2026-3914 is an integer overflow vulnerability in the WebML component of Google Chrome prior to version 146.0.7680.71. The flaw allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. It maps to CWE-190 (Integer Overflow or Wraparound) and CWE-472 (External Control of Assumed-Immutable Web Parameter), with 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), rated as High severity by Chromium security.
A remote attacker can exploit this vulnerability by tricking a user into visiting a malicious website, requiring no privileges but relying on user interaction. Successful exploitation enables heap corruption, potentially leading to arbitrary code execution with high impacts on confidentiality, integrity, and availability.
Google addressed the issue in the stable channel update for Desktop Chrome to version 146.0.7680.71, as announced in the Chrome Releases blog post dated March 2026. Additional details are available in the Chromium issue tracker entry at issues.chromium.org/issues/481776048.
This vulnerability affects WebML, the web standard for machine learning model execution in browsers, highlighting risks in emerging AI/ML web features. No public reports of real-world exploitation are noted as of the CVE publication on 2026-03-11.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-11420
Vulnerability Data
Integer overflow in WebML in Google Chrome prior to 146.0.7680.71 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
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
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.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.