EUVD-2026-105698
GHSA-826x-5jv4-g9hg
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger memory corruption in Sync component
-
ImpactExecute arbitrary code within renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
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 | Requires the victim to load attacker-controlled content - a crafted HTML page - in a vulnerable Chrome build prior to 156.0.8078.47, matching CVSS UI:R; no authentication or special privileges are needed (PR:N). The principal limiting factor is that resulting code execution is confined to the Chrome renderer sandbox, so impact beyond the sandbox requires chaining with a separate sandbox-escape vulnerability. Exploitation targets the Sync component's memory handling; it affects default desktop Chrome configurations but depends on the user actively visiting the malicious page rather than any passive/automatic trigger. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity, unauthenticated bug that requires user interaction - consistent with the description's 'crafted HTML page' delivery, i.e. a victim must browse to attacker content. Critically, the description states code executes 'inside the sandbox,' so this is NOT a full host compromise on its own; it would need to be chained with a sandbox-escape to achieve system-level impact, and the CVSS scope is correctly Unchanged (S:U). This tension is notable: the high C/I/A values reflect arbitrary code execution in the renderer process, but Chromium's own security severity rating is 'Low,' signaling the vendor views the real-world impact as constrained by sandbox containment - a meaningful conflict between the 8.8 numeric score and vendor-assessed severity. No EPSS score, no CISA KEV listing, and no POC were provided in the input; exploitation status is therefore 'no public exploit identified at time of analysis.' Net assessment: patch promptly as part of normal Chrome update cadence given ubiquitous deployment and unauthenticated network vector, but this is not a drop-everything emergency absent evidence of active exploitation or a paired sandbox escape. |
| Exploit ScenarioDerived | An attacker lures a victim to a malicious or compromised web page containing crafted content that triggers memory corruption in Chrome's Sync component, achieving arbitrary code execution within the renderer sandbox. Because exploitation needs the user to visit the page (UI:R) and the code runs confined to the sandbox, a practical full-system attack would require chaining this with a separate sandbox-escape bug. No public proof-of-concept was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in Google Chrome's Sync component before 156.0.8078.47 allows remote attackers to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The issue is network-reachable and unauthenticated per the CVSS vector, but exploitation requires user interaction, and code execution is confined to Chrome's sandbox unless chained with a separate sandbox escape. No public exploit was identified at time of analysis, and Google has released a fixed Chrome build.
RemediationAI
Vendor-released patch: update Google Chrome to 156.0.8078.47 or later through the Stable channel, then restart the browser and verify the installed version at chrome://settings/help. The vendor advisory is https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the associated Chromium issue is https://issues.chromium.org/issues/513394775. No validated vendor workaround is specified; disabling Sync may reduce exposure to the Sync component but is not established as a complete fix and will disrupt profile synchronization, while restricting users to trusted sites reduces the likelihood of visiting crafted HTML but is impractical as a general control. Enterprise administrators should enforce the fixed version through browser management and verify fleet compliance after deployment.
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
CVE-2026-113004 is classified as CWE-119, improper restriction of operations within the bounds of a memory buffer, in Chrome's Sync component. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H indicates a low-complexity, network-delivered flaw requiring the victim to open attacker-controlled HTML, with high confidentiality and integrity impact if code execution succeeds. The independent assessment notes that execution is constrained by Chrome's multi-process renderer sandbox, so host compromise would require a separate sandbox-escape vulnerability; this is consistent with the description's statement that arbitrary code executes inside the sandbox. Google's Chromium security severity is listed as Low while the provided CVSS base score is 8.8; the higher score reflects potential code-execution impact, while the sandbox and user-interaction requirement are important limiting factors. No CPE strings were provided, but the affected-version and advisory data identify Chrome desktop builds prior to 156.0.8078.47.
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 needs victim browsing (AV:N, UI:R) with no auth (PR:N); arbitrary code execution gives high C/I/A, but sandbox containment keeps scope Unchanged (S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Sync in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
A high-severity memory-corruption flaw in Google Chrome's Sync component (CVE-2026-113004) could let an attacker run code on an employee's machine when they simply visit a malicious or compromised web page, affecting anyone using an unpatched Chrome build across the organization. Google has already shipped a fixed build and no public exploit code has surfaced, so the exposure window is driven almost entirely by how quickly our browser fleet is updated. Leadership should care because Chrome is our primary attack surface for phishing-driven compromise, and the contained-to-sandbox nature of the flaw means risk is real but materially reduced unless paired with a second exploit.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Exploit-DB