Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish network interception position
-
DeliveryDeliver crafted network traffic to victim's Chrome session
-
ExploitTrigger HttpsUpgrades protection mechanism failure
-
ExecutionBypass web origin policy enforcement
-
ImpactRead limited cross-origin content from victim's browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Exploitation requires a victim running Google Chrome prior to 152.0.7977.65 and active user interaction with web content (UI:R per CVSS vector), meaning the victim must be actively browsing rather than passively connected. The CVSS AV:N vector indicates network exploitability without requiring physical proximity; however, the nature of the HttpsUpgrades bypass suggests the attacker benefits from the ability to influence network traffic between the victim and remote servers, such as a man-in-the-middle position or a malicious server serving crafted responses. No attacker authentication or elevated privileges are required (PR:N). Impact is strictly limited to partial confidentiality disclosure (C:L) - no data modification or service disruption is achievable through this vulnerability. Exploitation is further constrained to Chrome desktop versions; mobile Chrome and other Chromium-based browsers are not confirmed affected by this specific advisory. |
| Impact | The CVSS 3.1 base score of 4.3 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N accurately reflects a moderate-severity finding: network-reachable, low complexity, no privileges required, but constrained by mandatory user interaction and limited to partial confidentiality impact with no integrity or availability consequences. The EPSS score of 0.26% at the 18th percentile is consistent with this assessment and suggests the vulnerability has not attracted significant exploit development interest. The 'Authentication Bypass' tag in the intelligence metadata is somewhat misleading - this is a web origin policy bypass, not a traditional authentication bypass, and the CVSS PR:N metric reflects lack of required attacker privileges rather than a bypass of user authentication. No KEV listing and no public exploit code further reinforce that operational risk is currently low. The missing detail is whether the HttpsUpgrades feature is enabled by default in all Chrome configurations or only in specific deployment modes; if it can be disabled by enterprise policy, managed environments may have reduced exposure. |
| Exploit ScenarioDerived | An attacker positioned to inject or manipulate network traffic - for example via a rogue Wi-Fi access point or a compromised network path - serves crafted HTTP responses designed to trigger a failure in Chrome's HttpsUpgrades mechanism. When a victim user on an unpatched Chrome instance browses normally and their traffic passes through this attacker-influenced network segment, the origin policy bypass takes effect, allowing the attacker to read a limited portion of cross-origin response content. No public exploit code for this specific issue has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
HttpsUpgrades protection mechanism failure in Google Chrome prior to 152.0.7977.65 enables remote attackers to bypass the browser's web origin policy via crafted network traffic. The vulnerability affects all desktop Chrome installations before the patched stable channel release and requires user interaction to trigger, consistent with CVSS UI:R. No public exploit code has been identified and no CISA KEV listing exists; the EPSS score of 0.26% (18th percentile) indicates low current exploitation probability.
RemediationAI
Upgrade Google Chrome to version 152.0.7977.65 or later, the patched stable channel release documented at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome's auto-update mechanism will apply this to most consumer endpoints automatically; enterprise administrators should verify deployment via Chrome Browser Cloud Management or Group Policy to confirm fleet-wide update status. As a compensating control prior to patching, enforcing HTTPS-only browsing via browser enterprise policy (chrome://flags or managed policy HttpsOnlyMode) reduces the attack surface by restricting the conditions under which the HttpsUpgrades mechanism operates - note this may break access to legacy HTTP-only internal resources and should be tested before broad rollout. Network-level HSTS preloading does not substitute for this browser-side fix.
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 affected component is Chrome's HttpsUpgrades subsystem - the mechanism responsible for automatically upgrading plaintext HTTP connections to HTTPS before they are sent. CWE-693 (Protection Mechanism Failure) identifies the root cause as a failure of this security enforcement layer, allowing crafted network traffic to circumvent it. When the upgrade mechanism is bypassed, the browser's web origin policy - the same-origin policy that isolates cross-origin resources - can be subverted, enabling a limited confidentiality disclosure. The affected product is identified via CPE as cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome versions prior to 152.0.7977.65 across desktop platforms.
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:L/I:N/A:N
Network-exploitable via crafted traffic requiring user interaction; impact is limited to partial confidentiality disclosure with no integrity or availability effect.
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
Protection mechanism failure in HttpsUpgrades in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to bypass web origin policy via crafted network traffic. (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-693 – Protection Mechanism Failure
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-65870
GHSA-x59q-wjwf-gr37
NVD
CVE.org
EPSS
Exploit-DB