Skip to main content

Google Chrome EUVDEUVD-2026-66045

| CVE-2026-79123 MEDIUM
Improper Input Validation (CWE-20)
2026-08-25 Chrome GHSA-phjg-2gh4-jcqf
Medium
Disputed · 6.5 Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise Chrome renderer via separate N-day or 0-day
  2. Delivery
    Craft malicious HTML page targeting NTP Footer
  3. Exploit
    Deliver page to victim browser session
  4. Execution
    Trigger improper input validation in NTP Footer
  5. Persist
    Bypass web origin policy
  6. Impact
    Manipulate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Chrome 152.0.7977.65 <152.0.7977.65

Affected Packages

euvd chrome fix: 152.0.7977.65

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)
Vendor (Chrome) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
vuln.today AI 5.3 MEDIUM

AC:H reflects the mandatory pre-condition of renderer process compromise; all other metrics align with the official vector.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
SUSE CRITICAL

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

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

3
CVSS changed
Aug 26, 2026 - 20:23 NVD
6.5 (MEDIUM)
CVE Published
Aug 25, 2026 - 20:10 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 25, 2026 - 20:10 cve.org
MEDIUM 6.5

DescriptionCVE.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

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Ubiquitous
dominant desktop browser deployed across billions of Windows endpoints
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Vendor 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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy