Skip to main content

Google Chrome EUVDEUVD-2026-111457

| CVE-2026-118345 HIGH
Use After Free (CWE-416)
2026-10-27 chrome-cve-admin@google.com GHSA-j9vf-mqj6-cvh8
8.8
CVSS 3.1 · Vendor: google
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to malicious web page
  2. Delivery
    Deliver crafted PDF/HTML to PDFium
  3. Exploit
    Trigger use-after-free in PDFium
  4. Execution
    Reuse freed object for control flow
  5. Impact
    Execute 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Chrome 156.0.8078.73 <156.0.8078.73

Affected Packages

euvd chrome fix: 156.0.8078.73

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

Vendor (google) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

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.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Oct 28, 2026 - 14:22 NVD
8.8 (HIGH)
CVE Published
Oct 27, 2026 - 23:17 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 27, 2026 - 23:17 cve.org
HIGH 8.8

DescriptionCVE.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

Why It Matters

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.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Ubiquitous
Google Chrome is one of the most widely deployed browsers worldwide
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy