Skip to main content

Google Chrome EUVDEUVD-2026-93710

| CVE-2026-106402 MEDIUM
Incorrect Authorization (CWE-863)
2026-10-06 Chrome GHSA-78x8-pwcw-qpf5
4.8
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

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

  1. Access
    Craft malicious Chrome extension
  2. Delivery
    Social-engineer victim into installing it
  3. Exploit
    Abuse incorrect authorization in Extensions
  4. Execution
    Spoof trusted UI elements
  5. Impact
    Deceive user into unsafe action

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 requires the attacker to (1) build a crafted Chrome extension and (2) use social engineering to get the victim to install it in Chrome versions prior to 155.0.8059.39; the installed extension then leverages incorrect authorization in the Extensions component to spoof UI elements. Limiting factors: the victim must actively install an untrusted extension (bypassing Chrome Web Store/enterprise install controls and user warnings), the attack is complex (CVSS AC:H), and impact is confined to deceptive UI spoofing rather than code execution or direct data compromise. Environments that restrict extension installation via enterprise policy are largely protected.

Impact

This is a genuinely low-to-moderate priority issue despite being network-reachable. The provided CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L, base 4.8) scores it Medium, consistent with Chromium's own 'Medium' severity rating and CWE-863 (Incorrect Authorization). The high attack complexity (AC:H) and the description's reliance on social engineering materially reduce real-world exploitability. CONFLICT TO VERIFY: the CVSS vector sets UI:N (no user interaction), yet the description explicitly states the attack requires 'social engineering' and 'a crafted Chrome extension' - i.e., the victim must be convinced to install an attacker-controlled extension. That is user interaction, so UI:N appears understated; treat the attack as interaction-dependent rather than fully automatic. No EPSS score, no CISA KEV listing, and no public exploit were provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The impact is UI spoofing (deceptive interface), not code execution or data theft, further limiting severity. Net: a real but low-urgency bug; patch in the normal Chrome update cycle rather than emergency response.

Exploit ScenarioDerived

An attacker publishes or sideloads a crafted Chrome extension and uses social engineering (phishing, fake 'required plugin' prompts) to persuade a victim to install it. Once installed, the extension abuses incorrect authorization to spoof trusted browser UI elements, deceiving the user into trusting attacker-controlled content or actions. No public exploit code was 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 the Extensions component of Google Chrome prior to 155.0.8059.39 allows a crafted extension to spoof browser UI elements after it has been installed, giving a remote attacker a means of deceiving the user about what the browser is actually showing or requesting. Successful exploitation requires social engineering to convince the victim to install an untrusted extension (the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N, Chromium severity Medium), so impact is limited to deceptive UI and low-level integrity loss rather than code execution or direct credential compromise, and unauthenticated remote attackers are the relevant threat model with user interaction as the practical gate. No public exploit code and no confirmed active exploitation were identified at time of analysis; environments that restrict extension installation through enterprise policy are largely protected, making this a genuinely low-to-moderate priority issue despite being network-reachable.

RemediationAI

Vendor-released patch: upgrade Google Chrome to 155.0.8059.39 or later - on managed fleets push the update through your software deployment tooling, and on unmanaged endpoints have users trigger the update from chrome://settings/help and confirm the displayed version; see the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html for release details. Where prompt patching is not possible, the effective compensating control is to remove the extension-installation avenue that exploitation depends on: enforce an ExtensionInstallAllowlist/ExtensionInstallBlocklist enterprise policy so only vetted extensions can be installed, disable developer mode loading of unpacked extensions, and block sideloading from untrusted sources - the trade-off is reduced user flexibility and additional helpdesk load when legitimate extensions need approval. Note that these controls defend against the precondition (social-engineered extension installation) rather than the authorization bug itself, so they should be treated as temporary until Chrome 155.0.8059.39 is deployed, and user awareness guidance about installing extensions only from trusted publishers remains relevant because no public exploit code was identified at time of analysis but the social engineering vector is inherently reusable.

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 flaw is an authorization error (CWE-863: Incorrect Authorization) in Chrome's Extensions subsystem - the code path that governs what an installed extension is permitted to do when interacting with browser UI surfaces. Chrome's extension platform relies on a permission and API-grant model (manifest-declared permissions, host permissions, and privileged extension APIs) to keep extension-supplied content from impersonating trusted browser chrome; when that authorization check is wrong, an extension can render content that appears to be genuine browser UI, enabling spoofing of prompts, dialogs, or other trust-bearing elements. The affected product is captured by the CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, i.e. all Google Chrome builds before the fixed release 155.0.8059.39; the EUVD record (EUVD-2026-93710) likewise lists the vulnerable range as versions below 155.0.8059.39. Because the primitive is deceptive UI rather than memory corruption or privilege escalation, the assessed impact stays at low confidentiality and integrity with no availability impact, and the AC:H rating reflects the requirement to first get a bespoke malicious extension installed past Chrome Web Store, enterprise, and user-facing installation safeguards - the attack is complex precisely because the extension installation step, not the authorization bug itself, is the hard part.

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 4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
vuln.today AI 4.2 MEDIUM

Social engineering to install a crafted extension means UI:R and AC:H; UI spoofing is primarily an integrity/limited-confidentiality deception with no availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/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
Low
Integrity
None
Availability
Low

Lifecycle Timeline

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

DescriptionCVE.org

Incorrect authorization in Extensions in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to spoof UI elements via a crafted Chrome extension. (Chromium security severity: Medium)

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Ubiquitous
Google Chrome is the dominant desktop browser across most environments
Data Quality
6 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

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
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