Skip to main content

Google Chrome CVE-2026-78968

| EUVDEUVD-2026-66049 MEDIUM
Missing Authorization (CWE-862)
2026-08-25 Chrome GHSA-fqw9-5q8w-m493
6.5
CVSS 3.1 · Vendor: Chrome
Share

Severity by source

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 prerequisite of prior renderer compromise; all other metrics follow the vendor vector as integrity-only, user-interaction-required, network-delivered.

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

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

4
Analysis Generated
Aug 26, 2026 - 20:27 vuln.today
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

Missing authorization in Core in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially spoof address bar via a crafted HTML page. (Chromium security severity: Low)

AnalysisAI

Address bar spoofing in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to deceive users about the current page origin via a crafted HTML page. The root cause is missing authorization (CWE-862) in Chrome Core, where the renderer can influence address bar state without proper permission checks. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Exploit separate renderer vulnerability
Delivery
Gain renderer process code execution
Exploit
Load crafted HTML page
Execution
Trigger missing authorization check in Chrome Core
Persist
Spoof address bar to trusted origin
Impact
Conduct phishing or credential theft

Vulnerability AssessmentAI

Exploitation Exploitation requires that the attacker has already achieved compromise of the Chrome renderer process through a separate, prior vulnerability - this is not a standalone initial-access vector. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The provided CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) overstates ease of exploitation by omitting the critical prerequisite: the attacker must have already achieved renderer process compromise before this flaw is exploitable. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who has separately exploited a renderer-process vulnerability (e.g., a V8 or Blink memory corruption bug) then serves a crafted HTML page that abuses the missing authorization check to rewrite the address bar, displaying a trusted origin (such as a banking domain) while the user is actually on attacker-controlled content. This enables high-confidence phishing or credential harvesting against users who rely on the address bar as a trust signal. …
Remediation Upgrade Google Chrome to version 152.0.7977.65 or later, which contains the vendor-released patch addressing this missing authorization check. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-78968 vulnerability details – vuln.today

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