Sandboxed code execution via crafted PDF
Published Apr 15, 2026 · Updated Apr 15, 2026
Heap buffer overflow in PDFium in Google Chrome before 147.0.7727.101 allows remote attackers to execute code via a crafted PDF file. Google identifies the faulty component only as PDFium; the restricted issue does not disclose which parser operation writes beyond its allocated heap buffer. A user must open or render attacker-controlled PDF content, and resulting code execution remains inside Chrome's sandbox.
Summary
What happened
Heap buffer overflow in PDFium in Google Chrome before 147.0.7727.101 allows remote attackers to execute code via a crafted PDF file. Google identifies the faulty component only as PDFium; the restricted issue does not disclose which parser operation writes beyond its allocated heap buffer. A user must open or render attacker-controlled PDF content, and resulting code execution remains inside Chrome's sandbox.
The record
- CVE
- CVE-2026-6305
- Published
- Apr 15, 2026
- Updated
- Apr 15, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-122, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2026CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=147.0.7727.101 <147.0.7727.101
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