Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCompromise Chrome renderer via separate N-day or 0-day
-
DeliveryCraft malicious HTML page targeting NTP Footer
-
ExploitDeliver page to victim browser session
-
ExecutionTrigger improper input validation in NTP Footer
-
PersistBypass web origin policy
-
ImpactManipulate or exfiltrate cross-origin content
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 that the attacker has already compromised the Chrome renderer process through a separate, unrelated vulnerability - this is an explicit precondition stated in the CVE description ('remote attacker who had compromised the renderer process'). Additionally, user interaction is required (UI:R per CVSS), meaning a victim must visit or be redirected to a crafted HTML page. The vulnerability is Windows-specific; Chrome on macOS, Linux, or mobile platforms is not named as affected. These two limiting factors - prior renderer compromise and user interaction - mean this cannot be exploited as a standalone remote attack against default Chrome configurations. |
| Impact | CVSS 3.1 scores this at 6.5 (Medium) with AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, but that vector materially overstates ease of exploitation: the official description requires prior renderer process compromise, a significant pre-condition that AC:L does not capture. Chromium's own severity rating is Low. EPSS at 0.18% (8th percentile) corroborates low real-world exploitation probability. No CISA KEV listing and no public POC have been identified. The actual risk is best understood as a component in an exploit chain - an attacker who has already broken the renderer sandbox may leverage this to further cross-origin boundaries, but this vulnerability alone does not grant initial access. Security teams should prioritize patching as part of routine Chrome update cadence rather than treating this as an emergency response item. |
| Exploit ScenarioDerived | An attacker who has separately exploited a renderer-process vulnerability in Chrome on Windows crafts an HTML page that feeds malformed input to the NTP Footer component; the validation failure allows cross-origin policy to be circumvented, enabling the attacker to read or manipulate content belonging to a different web origin from within the already-compromised renderer. No public POC exists, so this scenario requires chaining with an independent renderer exploit, substantially raising the bar for real-world exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Web origin policy bypass in Google Chrome on Windows (prior to 152.0.7977.65) via improper input validation in the New Tab Page (NTP) Footer component enables integrity compromise without confidentiality loss. Exploitation is contingent on the attacker having already achieved renderer process compromise, making this a chained, post-exploitation primitive rather than a standalone vector. No public exploit code exists and EPSS sits at the 8th percentile, consistent with Chromium's own Low severity rating - though the integrity impact is rated High under CVSS.
RemediationAI
Upgrade Google Chrome on Windows to version 152.0.7977.65 or later, which contains the vendor-released patch per the Chrome Stable Channel update published at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome's auto-update mechanism will apply this fix in most enterprise and consumer environments without manual intervention; administrators should verify managed deployments have propagated the update. Because exploitation requires prior renderer compromise, organizations that enforce Chrome's built-in site isolation features (Strict Site Isolation via enterprise policy) and keep all Chrome components current will substantially reduce chained exploit risk. No workaround is sufficient as a substitute for patching given Chrome's update model.
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 the NTP (New Tab Page) Footer in Google Chrome on Windows, identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*. CWE-20 (Improper Input Validation) indicates the root cause is insufficient sanitization or boundary-checking of attacker-controlled input within the NTP Footer rendering path. Web browsers enforce a Same-Origin Policy (SOP) to prevent cross-origin data access; a bypass here allows a malicious page hosted in a compromised renderer to violate origin isolation and manipulate content or state belonging to a different origin. The renderer process in Chrome operates within a sandbox; this vulnerability presupposes that sandbox has already been defeated, placing the exploit firmly in a privilege-escalation or sandbox-bypass chaining context rather than an initial-access scenario.
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:H/A:N
AC:H reflects the mandatory pre-condition of renderer process compromise; all other metrics align with the official vector.
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
Improper input validation in NTP Footer in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (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.
Same weakness CWE-20 – Improper Input Validation
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-66045
GHSA-phjg-2gh4-jcqf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB