Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessExploit separate renderer-process vulnerability
-
DeliveryAchieve renderer code execution
-
ExploitServe crafted HTML page to victim
-
ExecutionTrigger Downloads privilege management flaw
-
PersistSpoof browser address bar URL
-
ImpactDeceive user via phishing interaction
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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 two hard prerequisites: (1) the attacker must have already achieved code execution within the Chrome renderer process via a separate, independent vulnerability, and (2) user interaction with a crafted HTML page is required (UI:R). The renderer compromise cannot be bypassed - this vulnerability is not exploitable as a standalone network-level attack. Exploitation is limited to Chrome desktop versions prior to 152.0.7977.75. No special browser configuration or non-default feature is required beyond running a vulnerable Chrome build; the flaw is in the core Downloads component. |
| Impact | The CVSS 4.2 score (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L) correctly encodes the high attack complexity imposed by the mandatory renderer compromise prerequisite. However, the I:N metric is inconsistent with address bar spoofing, which by definition falsifies information displayed to the user - a form of integrity impact that should register as at least I:L. The A:L metric in the provided vector also lacks an obvious basis for a pure UI-spoofing vulnerability; both metric assignments should be verified against the upstream Chromium bug report. No EPSS data was provided, and the vulnerability does not appear in CISA KEV. Chromium's own Medium severity rating aligns with the CVSS score and reflects the two-bug-chain requirement. The realistic risk is constrained: exploitation demands a separate renderer exploit, making standalone targeting impractical, though address bar spoofing is a well-known second-stage technique for defeating user trust verification in chained browser exploit chains. |
| Exploit ScenarioDerived | An attacker first exploits a separate renderer-process vulnerability - such as a memory corruption bug in the V8 JavaScript engine or a Blink DOM handler - to gain code execution within Chrome's sandboxed renderer. From that compromised renderer, they serve a crafted HTML page that triggers the Downloads privilege management flaw, causing the browser address bar to display an attacker-controlled URL. The spoofed address bar then deceives the victim into believing they are interacting with a trusted domain, enabling credential phishing or further social engineering. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
Address bar spoofing in Google Chrome's Downloads component (versions prior to 152.0.7977.75) is reachable only after an attacker has already achieved code execution within the renderer process, enabling display of a falsified URL via a crafted HTML page. The flaw stems from improper privilege management (CWE-269) in the Downloads subsystem, which fails to enforce the privilege boundary between the sandboxed renderer and the trusted browser UI. No public exploit identified at time of analysis; a vendor-released patch is available in Chrome 152.0.7977.75.
RemediationAI
Update Google Chrome to version 152.0.7977.75 or later, which is the vendor-released fix announced in the September 2026 stable channel update at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop.html. Enterprise administrators should enforce Chrome updates via Group Policy (Windows) or fleet management tooling such as Chrome Browser Cloud Management. No configuration-level workaround exists to disable the vulnerable Downloads privilege path without removing core browser functionality; patching is the only effective mitigation.
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
Google Chrome's multi-process architecture isolates web content in sandboxed renderer processes, which are designed to have no influence over privileged browser-process UI elements such as the address bar. CWE-269 (Improper Privilege Management) in the Downloads component indicates that this privilege boundary is not correctly enforced: a compromised renderer can influence the address bar display in a way it should not be permitted to. This is a second-stage exploit primitive - the attacker must first compromise the renderer (typically via a memory corruption bug in components such as V8 or Blink) and then use this flaw to extend impact to the browser's trusted UI layer. Affected versions are Chrome desktop builds prior to 152.0.7977.75, confirmed by the EUVD affected-version range.
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
Sources disagree (Medium–Critical)AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L
Renderer compromise prerequisite justifies AC:H; spoofing falsifies displayed URL warranting I:L over I:N; no meaningful availability impact from address-bar deception alone.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Improper privilege management in Downloads in Google Chrome prior to 152.0.7977.75 allowed a remote attacker who had compromised the renderer process to spoof address bar via a crafted HTML page. (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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Related Vulnerabilities in Google Chrome 152 Memory Safety and Authorization Flaws
View all 26Same weakness CWE-269 – Improper Privilege Management
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-69743
GHSA-2cvv-4hfg-3c48
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB