Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition to send crafted network traffic
-
ExploitTarget Chrome Sync authorization check
-
ExecutionBypass incorrect authorization (CWE-863)
-
ImpactExfiltrate sensitive synced data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: 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 specifically targets the Sync feature of Google Chrome, so the victim must be using Chrome's Sync functionality for synced sensitive information to be exposed; installations with Sync disabled are not meaningfully affected. The flaw is remote and unauthenticated (PR:N, UI:N - no user interaction required), but the CVSS High attack complexity (AC:H) indicates a significant limiting factor: the attacker must satisfy conditions outside their control (e.g., a specific race, state, or network-position dependency) rather than reliably triggering the incorrect authorization on demand. Impact is strictly confidentiality (C:H, I:N, A:N) - disclosure of sensitive synced data only, with no code execution, data tampering, or denial of service. All versions of Chrome prior to 155.0.8059.39 are affected. |
| Impact | This is a genuinely moderate-priority issue, not an inflated high-CVSS item. All signals align downward: the provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) yields 5.9, driven entirely by a High confidentiality impact (C:H) but tempered by High attack complexity (AC:H), meaning exploitation requires specific conditions or a race/state that the attacker does not fully control. The CISA SSVC framework reinforces this: Exploitation=none (no observed activity), Automatable=no (cannot be reliably scripted at scale), and Technical Impact=partial (confidentiality-only, no integrity or availability loss). There is no CISA KEV listing and no EPSS score was provided in the input, so widespread-exploitation probability cannot be quantified - but the SSVC 'none/no' combination strongly suggests this is not under active or automated attack. Chromium's own severity rating is Medium, consistent with the 5.9 base score. The one amplifying factor is prevalence: Chrome is ubiquitous, so even a medium-severity authorization flaw in the Sync feature has an enormous installed base. Net assessment: patch on a normal cadence; this is not an emergency. No conflicting signals were found between the CVSS vector and the description - both indicate remote, high-complexity, confidentiality-only impact. |
| Exploit ScenarioDerived | A remote attacker crafts and sends specially-formed network traffic to a victim's Chrome Sync data flow, exploiting an incorrect-authorization check (CWE-863) to read sensitive synced information they should not be authorized to access. Because attack complexity is High, success depends on specific timing or state conditions outside the attacker's direct control, and no public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Incorrect authorization in Google Chrome's Sync feature (all versions prior to 155.0.8059.39) allows a remote, unauthenticated attacker to obtain sensitive synced information via crafted network traffic, although the High attack complexity rating indicates the attacker must satisfy conditions outside their control rather than reliably triggering the flaw on demand. Only users with Chrome Sync enabled are meaningfully exposed, and impact is limited to confidentiality disclosure of synced data with no code execution, tampering, or denial of service. No public exploit code has been identified at time of analysis, CISA's SSVC framework records no known exploitation, and a vendor patch is available.
RemediationAI
Vendor-released patch: Google Chrome 155.0.8059.39. Upgrade Chrome to 155.0.8059.39 or later through the built-in updater or by downloading the current stable build; the fix is documented in the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html and the Chromium issue at https://issues.chromium.org/issues/496623893. As a compensating control for environments that cannot immediately patch, disabling Chrome Sync prevents the exposure because installations with Sync disabled are not meaningfully affected, at the trade-off of losing cross-device bookmark, password, and settings synchronization. No public exploit code has been identified, so emergency out-of-band action is not warranted, but standard browser patch cadence should be maintained.
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
The root cause is CWE-863, Incorrect Authorization, in Google Chrome's Sync subsystem, the component responsible for synchronizing bookmarks, passwords, history, and settings across a signed-in user's devices through Google's sync servers and encrypted channels. The CVSS:3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (5.9 Medium) describes a network-reachable, unauthenticated flaw requiring no user interaction but with high attack complexity and unchanged scope, yielding strictly confidentiality impact on synced data. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms that all Chrome releases before 155.0.8059.39 are in scope, and Google rated the Chromium security severity as Medium, consistent with the independent assessment that this is a genuinely moderate-priority issue rather than an inflated high-CVSS item.
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:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Remote via crafted network traffic (AV:N) with no auth or interaction (PR:N/UI:N); AC:H reflects uncontrolled trigger conditions; confidentiality-only disclosure gives C:H, I:N, A:N.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Incorrect authorization in Sync in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to obtain sensitive information via crafted network traffic. (Chromium security severity: Medium)
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-93855
GHSA-j5hp-376w-8594
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB