CVE-2026-15117 is a high-severity use-after-free vulnerability in the Payments component of Google Chrome. In affected versions prior to 150.0.7871.115, improper object lifetime handling in payment-related processing can leave a dangling reference that is subsequently reused, resulting in heap corruption. The issue can be triggered by a remote attacker using a crafted HTML page and a specially constructed payment workflow, provided the victim performs specific user-interface gestures during the interaction. The vulnerability affects Chrome’s browser-side payment functionality and is classified by Chromium as High severity.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability in Chrome's payments framework that could potentially be abused through crafted payment workflows.
A high-severity use-after-free vulnerability in Chrome's Payments component.
A high-severity use-after-free vulnerability in Chrome's Payments component.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.