CVE-2026-6361 is a high-severity heap-based buffer overflow in PDFium, the PDF rendering engine used by Google Chrome. The flaw affects Google Chrome on Windows prior to version 147.0.7727.101 and is triggered while processing a crafted PDF document, where PDFium writes more data into a heap-allocated buffer than the buffer can hold. This memory corruption condition can overwrite adjacent heap structures and enable control-flow manipulation within the browser renderer context. Exploitation requires a remote attacker to deliver a malicious PDF and convince the target user to open it in Chrome and engage in specific UI gestures. Successful exploitation results in arbitrary code execution inside the Chrome sandbox.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity heap buffer overflow vulnerability in PDFium in Google Chrome.
A heap-based buffer overflow in Google Chrome's PDFium PDF rendering engine that can allow remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF and performs specific UI gestures.
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.