Heap corruption via WebML integer overflow
Published Mar 11, 2026 · Updated Mar 11, 2026
Integer overflow in Google Chrome's WebML before 146.0.7680.71 allows remote attackers to corrupt heap memory through crafted HTML. Google identifies the affected component and flaw class, but the restricted Chromium issue does not disclose the overflowing calculation or malformed WebML input. Exploitation requires a user to load attacker-controlled HTML; successful heap corruption permits reading or modifying browser-accessible data and interrupting the browser process.
Summary
What happened
Integer overflow in Google Chrome's WebML before 146.0.7680.71 allows remote attackers to corrupt heap memory through crafted HTML. Google identifies the affected component and flaw class, but the restricted Chromium issue does not disclose the overflowing calculation or malformed WebML input. Exploitation requires a user to load attacker-controlled HTML; successful heap corruption permits reading or modifying browser-accessible data and interrupting the browser process.
The record
- CVE
- CVE-2026-3914
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-190, CWE-472, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=146.0.7680.71 <146.0.7680.71
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo