Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Heap buffer overflow in PDFium in Google Chrome

IdentifiersCVE-2026-6305CWE-122· Heap-based Buffer Overflow

CVE-2026-6305 is a high-severity heap buffer overflow in PDFium, the PDF rendering component used by Google Chrome. According to the provided content, the flaw affects Google Chrome versions prior to 147.0.7727.101. A remote attacker can trigger the vulnerability by supplying a crafted PDF file, leading to memory corruption during PDF processing. Successful exploitation allows arbitrary code execution inside Chrome’s sandbox.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in arbitrary code execution within the Chrome sandbox. The provided CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates high impact to confidentiality, integrity, and availability of the affected sandboxed process. Because execution is described as occurring inside the sandbox, the immediate impact is constrained to the renderer/sandbox context unless chained with an additional sandbox escape or privilege-boundary bypass.

Mitigation

If you can’t patch tonight, do this now.

Apply the vendor patch as soon as possible. Until updates are fully deployed, reduce exposure to untrusted PDF content, avoid opening unsolicited or untrusted PDF files in Chrome, and consider using enterprise controls to restrict or disable in-browser PDF handling where operationally feasible. Because the vulnerability requires user interaction with a crafted PDF, limiting delivery and opening of untrusted PDFs can reduce risk pending patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 147.0.7727.101 or later. The provided content states that versions prior to 147.0.7727.101 are affected and that Google fixed the issue in the April 15, 2026 Chrome Stable update.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.