Sandboxed code execution via PDFium heap overflow
Published Apr 15, 2026 · Updated May 26, 2026
Heap buffer overflow in PDFium in Google Chrome on Windows before 147.0.7727.101 allows remote attackers to execute code via a crafted PDF. Google identifies PDFium as the affected component but has not disclosed the vulnerable function or the precise operation that overflows a heap allocation. Exploitation requires the user to perform specific UI gestures, and the reported code execution remains inside the browser sandbox.
Summary
What happened
Heap buffer overflow in PDFium in Google Chrome on Windows before 147.0.7727.101 allows remote attackers to execute code via a crafted PDF. Google identifies PDFium as the affected component but has not disclosed the vulnerable function or the precise operation that overflows a heap allocation. Exploitation requires the user to perform specific UI gestures, and the reported code execution remains inside the browser sandbox.
The record
- CVE
- CVE-2026-6361
- Published
- Apr 15, 2026
- Updated
- May 26, 2026
- Vendor
- WebM Project
- Product
- Chrome
- Classifications
- CWE-122, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 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 version<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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started