Skip to main content

Google Chrome CVE-2026-78953

| EUVDEUVD-2026-65927 LOW
Missing Authorization (CWE-862)
2026-08-25 Chrome GHSA-qwmc-fc5p-qxxh
3.1
CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY
3.1 LOW
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
vuln.today AI
3.4 LOW

Site isolation is a cross-security-boundary control; bypassing it crosses into another origin's security domain, warranting S:C; renderer compromise prerequisite justifies AC:H.

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

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

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

Lifecycle Timeline

4
Analysis Generated
Aug 27, 2026 - 22:52 vuln.today
CVSS changed
Aug 27, 2026 - 20:37 NVD
3.1 (LOW)
CVE Published
Aug 25, 2026 - 20:10 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 25, 2026 - 20:10 cve.org
LOW 3.1

DescriptionCVE.org

Missing authorization in SiteIsolation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: Medium)

AnalysisAI

Site isolation boundary bypass in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to read cross-origin data via a crafted PDF file. This is a chained, second-stage attack technique - not a standalone exploit - requiring renderer process compromise as a hard prerequisite before the missing authorization check (CWE-862) in SiteIsolation becomes actionable. …

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
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Two sequential conditions are required: first, the attacker must achieve code execution within a Chrome renderer process via a separate, unrelated vulnerability - this is the primary limiting factor and a substantial barrier; second, the victim must interact with or be served a crafted PDF file within the same Chrome session (UI:R). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The official CVSS 3.1 score of 3.1 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) accurately reflects low real-world priority. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Update Google Chrome to version 152.0.7977.65 or later, as confirmed by the Google stable channel advisory (https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html). … Detailed patch versions, workarounds, and compensating controls in full report.

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

Share

CVE-2026-78953 vulnerability details – vuln.today

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