Skip to main content

Google Chrome EUVDEUVD-2026-93855

| CVE-2026-106222 MEDIUM
Incorrect Authorization (CWE-863)
2026-10-06 Chrome GHSA-j5hp-376w-8594
5.9
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

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

  1. Access
    Position to send crafted network traffic
  2. Exploit
    Target Chrome Sync authorization check
  3. Execution
    Bypass incorrect authorization (CWE-863)
  4. Impact
    Exfiltrate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 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

Chrome 155.0.8059.39 <155.0.8059.39

Affected Packages

euvd chrome fix: 155.0.8059.39

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

Vendor (Chrome) PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 5.9 MEDIUM

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.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Red Hat 6.5 MEDIUM

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

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

Lifecycle Timeline

4
CVSS changed
Oct 07, 2026 - 11:22 NVD
5.9 (MEDIUM)
Patch available
Oct 06, 2026 - 20:04 EUVD
CVE Published
Oct 06, 2026 - 18:41 cve.org
MEDIUM 5.9
CVE Published
Oct 06, 2026 - 18:41 cve.org
UNKNOWN (no severity yet)

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

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Ubiquitous
Google Chrome is the dominant desktop/mobile browser worldwide
Data Quality
7 sources
Confidence: High

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor StatusVendor

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