Process-memory disclosure via FileSystem out-of-bounds read
Published May 14, 2026 · Updated May 14, 2026
Out-of-bounds read in Google Chrome FileSystem before 148.0.7778.168 on Mac allows remote attackers to read process memory via crafted HTML. The FileSystem component reads beyond an allocated memory boundary, but Google has not disclosed the affected function or input-processing path. Exploitation requires a user on macOS to perform specific UI gestures on the attacker's page; the documented consequence is potentially sensitive memory disclosure only.
Summary
What happened
Out-of-bounds read in Google Chrome FileSystem before 148.0.7778.168 on Mac allows remote attackers to read process memory via crafted HTML. The FileSystem component reads beyond an allocated memory boundary, but Google has not disclosed the affected function or input-processing path. Exploitation requires a user on macOS to perform specific UI gestures on the attacker's page; the documented consequence is potentially sensitive memory disclosure only.
The record
- CVE
- CVE-2026-8543
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 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=148.0.7778.168 <148.0.7778.168
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