Sandboxed code execution via WebXR use-after-free
Published May 28, 2026 · Updated May 28, 2026
Use after free in WebXR in Google Chrome before 148.0.7778.216 allows remote attackers to execute arbitrary code inside its sandbox via crafted HTML. The public record identifies WebXR as the locus but does not disclose which object is freed or which later operation dereferences it. Exploitation requires a user to open a crafted HTML page; resulting execution remains confined to the Chrome sandbox, with no documented sandbox escape.
Summary
What happened
Use after free in WebXR in Google Chrome before 148.0.7778.216 allows remote attackers to execute arbitrary code inside its sandbox via crafted HTML. The public record identifies WebXR as the locus but does not disclose which object is freed or which later operation dereferences it. Exploitation requires a user to open a crafted HTML page; resulting execution remains confined to the Chrome sandbox, with no documented sandbox escape.
The record
- CVE
- CVE-2026-9995
- 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