Arbitrary code execution via Proxy use-after-free
Published May 28, 2026 · Updated May 28, 2026
Use-after-free in Google Chrome Proxy before 148.0.7778.216 allows remote attackers to execute arbitrary code through a crafted PAC script. Google identifies the Proxy component but has not disclosed which object is freed or how PAC processing subsequently accesses it. Exploitation requires Chrome to process an attacker-controlled PAC script; the published record does not establish a network-listening service or a no-interaction path.
Summary
What happened
Use-after-free in Google Chrome Proxy before 148.0.7778.216 allows remote attackers to execute arbitrary code through a crafted PAC script. Google identifies the Proxy component but has not disclosed which object is freed or how PAC processing subsequently accesses it. Exploitation requires Chrome to process an attacker-controlled PAC script; the published record does not establish a network-listening service or a no-interaction path.
The record
- CVE
- CVE-2026-9887
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The fscrypt Project
- Product
- 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 version<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.
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.
Contact us