Heap corruption via Payments use-after-free
Published Jul 8, 2026 · Updated Jul 8, 2026
Use-after-free in Payments in Google Chrome before 150.0.7871.115 allows remote attackers to corrupt heap memory via a crafted HTML page. The public record identifies the Payments component, but the restricted bug report leaves the freed object, stale reference, and triggering operation undisclosed. Exploitation requires convincing a user to perform specific UI gestures; successful heap corruption compromises browser confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Payments in Google Chrome before 150.0.7871.115 allows remote attackers to corrupt heap memory via a crafted HTML page. The public record identifies the Payments component, but the restricted bug report leaves the freed object, stale reference, and triggering operation undisclosed. Exploitation requires convincing a user to perform specific UI gestures; successful heap corruption compromises browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-15117
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 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=150.0.7871.115 <150.0.7871.115
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