Skip to main content
Vulnerability Database/CVE-2026-113022

CVE-2026-113022: Google Chrome PDFium RCE Vulnerability

CVE-2026-113022 is a memory corruption flaw in Google Chrome PDFium that enables remote attackers to execute arbitrary code within the sandbox through malicious HTML pages. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113022 Overview

CVE-2026-113022 is a memory corruption vulnerability in the PDFium component of Google Chrome before version 156.0.8078.47. A remote attacker can trigger the flaw by convincing a user to visit a crafted HTML page. Successful exploitation allows arbitrary code execution inside the Chrome renderer sandbox. The issue is tracked under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer) and affects the embedded PDF rendering engine used by Chromium-based browsers.

Critical Impact

Remote attackers can execute arbitrary code within the Chrome sandbox through a malicious HTML page containing crafted PDF content, placing user data and browser state at risk.

Affected Products

  • Google Chrome versions prior to 156.0.8078.47
  • PDFium component bundled with Chromium
  • Chromium-based browsers inheriting the vulnerable PDFium build

Discovery Timeline

  • 2026-10-20 - CVE-2026-113022 published to the National Vulnerability Database (NVD)
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-113022

Vulnerability Analysis

The vulnerability resides in PDFium, the open-source PDF renderer embedded in Google Chrome. Memory corruption occurs when PDFium processes a crafted PDF document delivered through an HTML page, for example via an <embed>, <iframe>, or direct navigation. An attacker who controls the PDF structure can corrupt heap or stack memory during parsing or rendering.

Exploitation requires user interaction, specifically loading an attacker-controlled page. The scope remains unchanged, meaning the impact is contained within the renderer process. However, the renderer still handles sensitive page content, cookies, and session state. Chromium rates the security severity as Medium, while the NVD assigns a High rating due to the potential for arbitrary code execution.

Root Cause

The root cause is classified under [CWE-119], an improper restriction of operations within the bounds of a memory buffer. PDFium's handling of certain PDF object structures fails to enforce correct size or lifetime constraints, resulting in memory corruption during document processing. The upstream fix landed in Chrome 156.0.8078.47 through the Chromium project. Technical specifics are tracked in Chromium Issue #494352583.

Attack Vector

Attackers deliver the exploit through a crafted HTML page that loads a malicious PDF via PDFium. Common delivery methods include phishing links, malvertising, compromised websites, and watering-hole campaigns. The attacker needs no prior privileges, but the victim must open or render the hostile content. Successful exploitation yields code execution inside the sandboxed renderer, which an attacker can chain with a sandbox escape to achieve full system compromise.

No public proof-of-concept exploit code is available for CVE-2026-113022 at the time of publication. See the Google Chrome Stable Update advisory for additional context.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-113022

Indicators of Compromise

  • Chrome renderer process crashes referencing PDFium modules during PDF rendering
  • Unexpected child processes spawned by chrome.exe after visiting PDF-hosting pages
  • Outbound connections from the renderer process to unfamiliar domains following PDF loads
  • Browser telemetry showing versions of Chrome below 156.0.8078.47 in use

Detection Strategies

  • Inventory browser versions across the fleet and flag endpoints running Chrome prior to 156.0.8078.47
  • Monitor endpoint telemetry for anomalous process trees originating from Chrome renderer processes
  • Correlate web proxy logs with navigations to untrusted sites hosting PDF content
  • Hunt for crash dumps containing PDFium stack frames, which can indicate exploitation attempts

Monitoring Recommendations

  • Collect browser version data through endpoint management and SIEM platforms for continuous exposure tracking
  • Enable crash reporting and forward Chrome crash metadata to centralized logging for analyst review
  • Alert on renderer processes attempting to write executable memory or load unexpected modules
  • Review DNS and HTTP telemetry for domains delivering PDF payloads shortly before anomalous Chrome behavior

How to Mitigate CVE-2026-113022

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
  • Force relaunch of Chrome after patch deployment to ensure the vulnerable PDFium build is unloaded
  • Audit Chromium-based browsers and derivatives for pending updates that incorporate the PDFium fix
  • Restrict access to untrusted PDF content through proxy filtering until patching is complete

Patch Information

Google released the fix in the Chrome Stable channel as version 156.0.8078.47. Administrators should deploy the update via enterprise management tooling or allow Chrome's auto-update to apply the patch. Full details are available in the Google Chrome Stable Update advisory and the associated Chromium Issue #494352583.

Workarounds

  • Disable the internal PDF viewer via the PdfLocalFileAccessAllowedForDomains and AlwaysOpenPdfExternally enterprise policies until patching completes
  • Enforce Chrome's Site Isolation and sandbox hardening settings to limit renderer impact
  • Block navigations to untrusted PDF-hosting domains at the web proxy or secure web gateway
  • Educate users to avoid opening PDF links from unverified sources during the remediation window
bash
# Example Chrome enterprise policy to route PDFs to an external viewer
# Windows registry path:
# HKLM\Software\Policies\Google\Chrome\AlwaysOpenPdfExternally = 1

# macOS plist example
defaults write com.google.Chrome AlwaysOpenPdfExternally -bool true

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.