Sandboxed code execution via PDF use-after-free
Published May 28, 2026 · Updated May 28, 2026
Use-after-free in Google Chrome's PDF component before 148.0.7778.216 allows remote attackers to execute code in its sandbox via a crafted PDF. The PDF component accesses an object after its backing memory has been freed, but the restricted Chromium issue does not identify the object or code path. Opening the crafted PDF requires user interaction; successful exploitation gains code execution only inside Chrome's sandbox, with no demonstrated sandbox escape.
Summary
What happened
Use-after-free in Google Chrome's PDF component before 148.0.7778.216 allows remote attackers to execute code in its sandbox via a crafted PDF. The PDF component accesses an object after its backing memory has been freed, but the restricted Chromium issue does not identify the object or code path. Opening the crafted PDF requires user interaction; successful exploitation gains code execution only inside Chrome's sandbox, with no demonstrated sandbox escape.
The record
- CVE
- CVE-2026-9957
- 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?
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.
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