Heap corruption via USB use-after-free
Published Apr 16, 2025 · Updated Apr 17, 2025
Use-after-free in Google Chrome's USB component before 135.0.7049.95 allows remote attackers to corrupt heap memory via crafted HTML. Google has not publicly disclosed the freed object, stale access path, or triggering USB operation, and the linked issue remains restricted. A user must load the page; successful memory corruption can crash the browser or provide a code-execution primitive subject to Chrome's sandbox.
Summary
What happened
Use-after-free in Google Chrome's USB component before 135.0.7049.95 allows remote attackers to corrupt heap memory via crafted HTML. Google has not publicly disclosed the freed object, stale access path, or triggering USB operation, and the linked issue remains restricted. A user must load the page; successful memory corruption can crash the browser or provide a code-execution primitive subject to Chrome's sandbox.
The record
- CVE
- CVE-2025-3620
- Published
- Apr 16, 2025
- Updated
- Apr 17, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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=135.0.7049.95 <135.0.7049.95
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