Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML page
-
DeliveryDelivers link via phishing or ad network
-
ExploitVictim opens page in unpatched Chrome
-
ExecutionNetwork authorization check incorrectly evaluated
-
PersistAttacker-controlled network action bypasses system restriction
-
ImpactLimited unauthorized integrity modification achieved
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 that the targeted user actively visits an attacker-controlled HTML page using Google Chrome prior to version 152.0.7977.65. The CVSS PR:N metric confirms no attacker authentication or account is needed, but UI:R is mandatory - the victim must open the malicious page; passive network exposure is insufficient. The impact is bounded to a low integrity violation (I:L) with no confidentiality or availability consequence, and S:U indicates no scope change beyond the browser's own security context. Non-default configurations are not required; any user browsing the web with a vulnerable Chrome version is potentially exposed. |
| Impact | The CVSS 3.1 score of 4.3 (Medium) reflects a network-accessible, low-complexity flaw requiring no attacker privileges but mandating user interaction (UI:R), with impact limited to low integrity (I:L) and no confidentiality or availability consequences. Google's own Chromium severity rating of Medium is consistent with this score. The EPSS score of 0.38% at the 31st percentile provides a low exploitation-probability signal, suggesting this vulnerability has not attracted significant attacker attention relative to the broader vulnerability population. KEV status is not confirmed and no public exploit code has been identified, making this a patch-on-schedule rather than emergency-response issue for most organizations. The UI:R requirement meaningfully constrains automated or mass exploitation, as passive network exposure alone is insufficient - a user must actively visit the attacker's page. |
| Exploit ScenarioDerived | An attacker registers or compromises a web domain and hosts a crafted HTML page designed to trigger Chrome's Network authorization flaw. The attacker delivers the link via phishing email or malvertising. When a user on a vulnerable Chrome version visits the page, the browser's authorization logic incorrectly permits a network-level action that should be blocked, enabling the attacker to achieve a limited unauthorized write or state modification within the browser's network context. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Incorrect authorization in Google Chrome's Network subsystem (all versions before 152.0.7977.65) permits remote unauthenticated attackers to bypass system access restrictions by inducing a user to visit a crafted HTML page. Classified as CWE-863, the flaw allows a limited integrity violation against the affected system without confidentiality or availability impact. No public exploit has been identified at time of analysis, and the low EPSS score (0.38%, 31st percentile) indicates minimal current exploitation pressure.
RemediationAI
Upgrade Google Chrome to version 152.0.7977.65 or later using Chrome's built-in updater or by downloading directly from the stable channel release advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Enterprise administrators should push this update via Google Admin Console or their preferred MDM/endpoint management tooling. Prior to patching, a compensating control is to enforce web content filtering to block untrusted or uncategorized domains at the network perimeter, reducing the likelihood users visit attacker-controlled HTML pages; however, this does not eliminate risk for users browsing unfiltered networks. Disabling JavaScript globally is a more complete workaround but carries significant usability impact and is impractical for most deployments.
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 vulnerability resides in Chrome's Network component and is rooted in CWE-863 (Incorrect Authorization) - a failure to correctly enforce access control decisions for network-level operations within the browser. The affected CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) covers all Chrome releases on all platforms prior to 152.0.7977.65. The attack surface is Chrome's rendering or network request pipeline, where a specially crafted HTML page can trigger an authorization check to be evaluated incorrectly, allowing the browser to access or relay a network resource that should be restricted under the user's security context.
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:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Network delivery via crafted HTML requiring active user visit; no attacker privileges needed; impact confined to low integrity with no confidentiality loss or scope change.
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: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Incorrect authorization in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to bypass system access restrictions 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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
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-65935
GHSA-mcm5-j3p7-m443
NVD
CVE.org
EPSS
Exploit-DB