Process-memory disclosure via undisclosed WebXR implementation
Published Jul 30, 2026 · Updated Jul 30, 2026
Information disclosure in WebXR in Google Chrome before 151.0.7922.72 allows remote attackers to read process memory via crafted HTML. Google identifies an inappropriate WebXR implementation, but published records do not disclose the faulty code path or operation that exposes memory. User interaction is required to load attacker-controlled HTML; the documented impact is process-memory disclosure without integrity or availability loss.
Summary
What happened
Information disclosure in WebXR in Google Chrome before 151.0.7922.72 allows remote attackers to read process memory via crafted HTML. Google identifies an inappropriate WebXR implementation, but published records do not disclose the faulty code path or operation that exposes memory. User interaction is required to load attacker-controlled HTML; the documented impact is process-memory disclosure without integrity or availability loss.
The record
- CVE
- CVE-2026-18005
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-200, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 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=151.0.7922.72 <151.0.7922.72
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