Sandboxed code execution via FedCM use-after-free
Published Mar 24, 2026 · Updated Mar 24, 2026
Use-after-free in FedCM in Google Chrome before 146.0.7680.165 allows remote attackers to execute arbitrary code inside the sandbox. Google identifies the affected locus only as FedCM; restricted bug details leave the freed object's lifetime error and triggering state transition undisclosed. A crafted HTML page and user interaction are required, and the reported code execution remains confined to Chrome's sandbox.
Summary
What happened
Use-after-free in FedCM in Google Chrome before 146.0.7680.165 allows remote attackers to execute arbitrary code inside the sandbox. Google identifies the affected locus only as FedCM; restricted bug details leave the freed object's lifetime error and triggering state transition undisclosed. A crafted HTML page and user interaction are required, and the reported code execution remains confined to Chrome's sandbox.
The record
- CVE
- CVE-2026-4680
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 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=146.0.7680.165 <146.0.7680.165
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