Heap corruption via PDFium use after free
Published May 28, 2026 · Updated May 28, 2026
Use after free in PDFium in Google Chrome before 148.0.7778.216 allows remote attackers to corrupt heap memory via a crafted PDF file. Google identifies the faulty operation only as use after free in PDFium and has not disclosed the affected class, function, or lifetime transition. Exploitation requires Chrome to process the attacker-supplied PDF; published details establish heap corruption but not code execution or sandbox escape.
Summary
What happened
Use after free in PDFium in Google Chrome before 148.0.7778.216 allows remote attackers to corrupt heap memory via a crafted PDF file. Google identifies the faulty operation only as use after free in PDFium and has not disclosed the affected class, function, or lifetime transition. Exploitation requires Chrome to process the attacker-supplied PDF; published details establish heap corruption but not code execution or sandbox escape.
The record
- CVE
- CVE-2026-10002
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=148.0.7778.216 <148.0.7778.216
What conditions does exploitation require?
What is affected?
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.
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