Out-of-sandbox memory disclosure via DataTransfer overread
Published Sep 17, 2026 · Updated Sep 17, 2026
Out-of-bounds read in DataTransfer in Google Chrome before 153.0.8010.52 allows local users to read memory outside the sandbox via a local program. The DataTransfer component reads beyond an intended memory boundary, but Google has not disclosed the specific code path or malformed input involved. Exploitation requires a local program and social engineering of a user; the published impact is memory disclosure.
Summary
What happened
Out-of-bounds read in DataTransfer in Google Chrome before 153.0.8010.52 allows local users to read memory outside the sandbox via a local program. The DataTransfer component reads beyond an intended memory boundary, but Google has not disclosed the specific code path or malformed input involved. Exploitation requires a local program and social engineering of a user; the published impact is memory disclosure.
The record
- CVE
- CVE-2026-93376
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- WebM Project
- Product
- Chrome
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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 version<153.0.8010.52
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started