Heap corruption via libvpx buffer overflow
Published Feb 3, 2026 · Updated Feb 3, 2026
Heap buffer overflow in libvpx in Google Chrome before 144.0.7559.132 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus as libvpx but has not published the malformed video input or incorrect memory operation that overruns the heap buffer. The network attack requires user interaction with attacker-controlled HTML; successful exploitation compromises browser confidentiality, integrity, and availability.
Summary
What happened
Heap buffer overflow in libvpx in Google Chrome before 144.0.7559.132 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus as libvpx but has not published the malformed video input or incorrect memory operation that overruns the heap buffer. The network attack requires user interaction with attacker-controlled HTML; successful exploitation compromises browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-1861
- Published
- Feb 3, 2026
- Updated
- Feb 3, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2026CVE publishedPublication date reported by the CVE source.
- Feb 3, 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=144.0.7559.132 <144.0.7559.132
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