Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to install crafted extension
-
DeliveryVictim installs malicious Chrome extension
-
ExploitExtension sends malformed input to Extensions handling
-
ExecutionBypass web origin policy into privileged page
-
ImpactIntegrity violation of privileged context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to install a crafted, attacker-controlled Chrome extension obtained through social engineering - the malicious extension is the exploitation vector, and the flaw is triggered when that extension abuses improper input validation in Chrome's Extensions handling to cross the web origin policy boundary into a privileged (e.g., chrome:// / WebUI) page. Limiting factors: mandatory user interaction (UI:R) to install and run the extension, dependence on tricking the user rather than any default-reachable network path, and the fact that Chrome's auto-update plus the vendor patch (155.0.8059.39) close the window; impact is confined to integrity (C:N/A:N), with no confidentiality loss or denial of service claimed. |
| Impact | This is a genuine but lower-tier priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, base 6.5 MEDIUM) describes a network-reachable, unauthenticated, low-complexity integrity-only issue - but the UI:R flag and the description's explicit reliance on social engineering are the dominant real-world limiters, because the attacker must first convince a victim to install and interact with a malicious Chrome extension. Google/Chromium themselves rated the security severity 'Low', which aligns with the low exploitation signals: EPSS is 0.18% (7th percentile), there is NO CISA KEV listing and NO public POC referenced, so exploitation status is 'no public exploit identified at time of analysis.' The signals are consistent rather than conflicting - moderate CVSS, very low EPSS, vendor 'Low' rating, and a mandatory user-interaction precondition all point the same direction. The one tension worth stating: CVSS is network-vector (AV:N) and PR:N (unauthenticated), which can read as 'remote unauth' danger, but the practical attack requires victim-side extension installation, so treat this as user-interaction-gated, not drive-by. Patch availability from Google plus Chrome's auto-update mechanism further reduce exposure window. |
| Exploit ScenarioDerived | An attacker publishes or sideloads a crafted Chrome extension and uses social engineering (phishing, fake tooling, deceptive install prompt) to persuade a victim to install it. Once running, the extension exploits improper input validation to bypass the web origin policy and reach a privileged Chrome page, violating the integrity boundary. No public exploit code or active exploitation is currently identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Improper input validation in Google Chrome's Extensions component before 155.0.8059.39 lets a crafted, attacker-controlled extension cross the web origin policy boundary and act within a privileged browser page (for example chrome:// or other WebUI surfaces), with the impact confined to integrity (C:N/I:H/A:N) per the assessed CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N. Exploitation is neither remote-automatic nor silent: the attacker must first convince the victim to install and run the malicious extension through social engineering, which is why Google rated it Low on the Chromium severity scale despite the 6.5 base score. EPSS sits at only 0.18 percent (7th percentile) and no public exploit has been identified at time of analysis, so this is a genuine but lower-tier priority; a vendor patch is available in Chrome 155.0.8059.39 and Chrome's auto-update channel rapidly closes the exposure window.
RemediationAI
Vendor-released patch: upgrade to Google Chrome 155.0.8059.39 or later - the fix ships in the stable channel release documented at chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html, with technical detail in issues.chromium.org/issues/553256068. On managed endpoints confirm the installed build via chrome://version and force the update through the Google Update service or your software deployment tooling, then restart the browser so the new binary is actually loaded; because Chrome auto-updates by default, most consumer installs will remediate themselves within days, which materially shrinks the exposure window. For endpoints that cannot be updated immediately, the effective compensating control is to constrain what extensions can run, since the exploitation vector is a user-installed malicious extension: use enterprise policy to enforce an ExtensionInstallAllowlist or ExtensionInstallBlocklist and disable ExtensionInstallSources for untrusted locations, and where feasible block developer-mode sideloading, with the trade-offs that this breaks legitimate unlisted extensions and adds administrative overhead for allowlist maintenance. User-awareness controls against social-engineering extension install prompts help but are not deterministic. If the update cannot be applied, consider restricting access to privileged chrome:// / WebUI surfaces through policy and monitoring extension installs for unexpected privilege-boundary activity; note that no public exploit code has been identified at time of analysis and EPSS is 0.18 percent (7th percentile), so these harder controls are best reserved for high-value or unmanaged-but-sensitive environments.
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 class is CWE-20, improper input validation, inside Chrome's Extensions subsystem rather than in a network-facing parser or renderer memory-safety path. Chrome enforces origin isolation so that extension pages, content scripts, and normal web content cannot read or manipulate privileged chrome:// / WebUI surfaces, which are treated as a trusted security boundary. The flaw here means a sufficiently crafted extension could supply input that the Extensions layer failed to validate correctly, allowing that extension to bypass the web origin policy and operate inside a privileged page. Consistent with the CPE entry cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, the issue is version-bounded and platform-agnostic, affecting Chrome builds below 155.0.8059.39 (EUVD-2026-93629 records the same pre-155.0.8059.39 affected range). Because the exploitation vector is the extension itself, the attacker's Chrome-side prerequisite is convincing a user to install it (UI:R), while the assessed vector shows no privilege requirement at the network layer (PR:N) and no confidentiality or availability impact, reflecting a policy/boundary bypass rather than memory corruption or data exfiltration. Chromium's own tracker entry (issues.chromium.org/issues/553256068) and the stable channel release notes are the authoritative technical references.
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:N/I:H/A:N
Network-delivered malicious extension needs no attacker privileges (PR:N) but requires victim installation/interaction (UI:R); impact is integrity-only (I:H) from bypassing origin policy into a privileged page, with no confidentiality or availability loss.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Improper input validation in Extensions in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to bypass web origin policy into a privileged page via a crafted Chrome extension. (Chromium security severity: Low)
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-93629
GHSA-w3jw-qgj6-vq39
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB