CVE-2026-3915

CVE-2026-3915 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-122.

Key facts

Description

Heap buffer overflow in WebML in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)

Frequently asked questions

What is CVE-2026-3915?
Heap buffer overflow in WebML in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)
How severe is CVE-2026-3915?
CVE-2026-3915 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-3915 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-3915?
CVE-2026-3915 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-3915?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-3915 have an EU (EUVD) identifier?
Yes. CVE-2026-3915 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11422.
When was CVE-2026-3915 published?
CVE-2026-3915 was published on 2026-03-11 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Chrome

All CVEs affecting Google Chrome →

Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities

Browse all CWE-122 (Heap-based Buffer Overflow) vulnerabilities →