Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
DeliveryDeliver crafted PDF/HTML to PDFium
-
ExploitTrigger use-after-free in PDFium
-
ExecutionReuse freed object for control flow
-
ImpactExecute arbitrary code inside renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to render a crafted HTML page that drives Chrome's built-in PDFium PDF engine (UI:R - user interaction such as visiting an attacker-controlled page is mandatory); it is remote and unauthenticated (PR:N) against default Chrome configurations prior to 156.0.8078.73, since PDFium is a standard bundled component. The key LIMITING factor is that resulting code execution is confined to the renderer sandbox per the vendor description - achieving full host compromise would require chaining an additional sandbox-escape vulnerability, which is not part of this CVE. The specific memory-management trigger within PDFium is not described in the available sources. |
| Impact | This is a genuine high-priority browser vulnerability, though not an emergency. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) indicates a network-reachable, low-complexity flaw that requires no privileges but does require user interaction (visiting or rendering a crafted page). Google assigns a 'High' Chromium severity and a patch is available, and the vuln.today decision label is 'this_week' - consistent with prompt, not emergency, remediation. Critically, the description states code execution occurs 'inside the sandbox,' meaning successful exploitation yields code execution in the constrained PDFium/renderer process and would still require a separate sandbox-escape to achieve full host compromise; the CVSS C:H/I:H/A:H reflects renderer-context impact (scope Unchanged), not root on the machine. No EPSS score was provided, so statistical exploitation likelihood cannot be quantified. The vulnerability is NOT listed in CISA KEV and there is no public exploit identified at time of analysis - the chromium issue tracker reference (issues.chromium.org/574061024) is a restricted-access bug entry, not a working PoC. Net: a real, broadly-exposed memory-corruption bug in ubiquitous software that should be patched promptly, but there is no evidence of active exploitation or public weaponization at this time. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing a crafted PDF document that triggers a use-after-free in Chrome's PDFium component when rendered. A victim with a vulnerable Chrome version (prior to 156.0.8078.73) visits the page, and the freed-object reuse is leveraged to execute attacker-controlled code within the renderer sandbox. No public exploit is identified at time of analysis, and full system compromise would additionally require a sandbox escape. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Use-after-free in PDFium, the PDF rendering engine bundled with Google Chrome, allows remote, unauthenticated attackers to potentially execute arbitrary code within the renderer sandbox when a victim renders a crafted HTML page in Chrome builds prior to 156.0.8078.73. The issue is rated high priority for this week's patch cycle rather than an emergency, a vendor fix exists in Chrome 156.0.8078.73, and no public exploit was identified at time of analysis. Per the vendor description, code execution is confined to the renderer sandbox; full host compromise would require chaining a separate sandbox-escape vulnerability that is not part of this CVE.
RemediationAI
Vendor-released patch: Google Chrome 156.0.8078.73. Upgrade through Chrome's built-in updater (Help > About Google Chrome) or the appropriate package manager for your platform, and verify the installed version afterward. Enterprise administrators should push the fixed build through their standard Chrome update mechanism. The authoritative references are the Chrome Releases stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html and the Chromium issue tracker at https://issues.chromium.org/issues/574061024. No workaround is documented in the available advisory data, so the vendor fix is the complete remediation; patching is prioritized for this week rather than as an emergency.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PDFium is the open-source PDF rendering library that Google Chrome ships as a standard bundled component, so exposure does not depend on a separate PDF application being installed. The root cause is a use-after-free (CWE-416): memory associated with a PDFium object is released while a reference to it remains, and a later dereference can corrupt memory and redirect execution. Because the flaw is reachable through content rendered by the browser, any crafted HTML page that drives PDFium is a potential attack surface. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) records a network-reachable issue with low attack complexity, no privileges required, mandatory user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The specific memory-management trigger within PDFium is not described in the available sources. The associated tags classify the issue as remote code execution, denial of service, and memory corruption, consistent with a use-after-free that can crash the renderer or, per the vendor severity assessment, potentially lead to arbitrary code execution; the described impact remains inside the renderer sandbox.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page reachable over the network with low complexity and no privileges, but requires the user to open it (UI:R); scope Unchanged as impact is within the sandboxed renderer.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in PDFium in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
A high-severity vulnerability in Google Chrome's PDF rendering engine could allow an attacker to execute code within the browser's sandbox when a user visits a malicious webpage. This primarily affects employees who use Chrome for web browsing, but the sandbox limits the damage to the browser process. Leadership should prioritize patching to maintain a strong security posture and prevent potential follow-on attacks that could exploit the sandbox.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-111457
GHSA-j9vf-mqj6-cvh8
NVD
CVE.org
EPSS
Exploit-DB