Renderer-compromise memory disclosure via use-after-free
Published May 14, 2026 · Updated May 14, 2026
Use-after-free in Google Lens in Google Chrome before 148.0.7778.168 allows remote attackers to read process memory via crafted HTML. Google identifies the component and memory-lifetime error, but the linked Chromium issue is restricted and no affected object or stale-reference operation is public. Exploitation requires prior renderer compromise; the bounded result is potentially sensitive process-memory disclosure, with no reported write or code-execution capability.
Summary
What happened
Use-after-free in Google Lens in Google Chrome before 148.0.7778.168 allows remote attackers to read process memory via crafted HTML. Google identifies the component and memory-lifetime error, but the linked Chromium issue is restricted and no affected object or stale-reference operation is public. Exploitation requires prior renderer compromise; the bounded result is potentially sensitive process-memory disclosure, with no reported write or code-execution capability.
The record
- CVE
- CVE-2026-8550
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416
- 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