Arbitrary memory access via GFX bounds failure
Published May 6, 2026 · Updated May 6, 2026
Out-of-bounds memory access in Google Chrome GFX before 148.0.7778.96 allows remote attackers to read and write memory via malicious network traffic. Google identifies GFX as the locus but has not published which operation omits the necessary bounds check; the linked Chromium issue is restricted. A user must cause Chrome to process attacker-controlled network content, and the published impact is limited to arbitrary memory reads and writes.
Summary
What happened
Out-of-bounds memory access in Google Chrome GFX before 148.0.7778.96 allows remote attackers to read and write memory via malicious network traffic. Google identifies GFX as the locus but has not published which operation omits the necessary bounds check; the linked Chromium issue is restricted. A user must cause Chrome to process attacker-controlled network content, and the published impact is limited to arbitrary memory reads and writes.
The record
- CVE
- CVE-2026-7950
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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.96 <148.0.7778.96
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