Sandboxed code execution via WebMCP use-after-free
Published Jul 23, 2026 · Updated Jul 23, 2026
Use after free in WebMCP in Google Chrome before 150.0.7871.186 allows remote attackers to execute code in the sandbox via crafted HTML. The restricted Chromium issue does not disclose the WebMCP object-lifetime error or the operation that reuses the freed object. A user must load attacker-controlled HTML; successful exploitation runs code within Chrome's sandbox, with no published sandbox escape.
Summary
What happened
Use after free in WebMCP in Google Chrome before 150.0.7871.186 allows remote attackers to execute code in the sandbox via crafted HTML. The restricted Chromium issue does not disclose the WebMCP object-lifetime error or the operation that reuses the freed object. A user must load attacker-controlled HTML; successful exploitation runs code within Chrome's sandbox, with no published sandbox escape.
The record
- CVE
- CVE-2026-16806
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 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=150.0.7871.186 <150.0.7871.186
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