Skip to main content

Google Chrome CVE-2026-79021

| EUVDEUVD-2026-66077 MEDIUM
Missing Authorization (CWE-862)
2026-08-25 Chrome GHSA-rgph-qwq5-gggr
Medium
Disputed · 6.5 Vendor: Chrome
View

Attack ChainAIDerived

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

  1. Recon
    Establish renderer-process code execution
  2. Delivery
    Craft malicious PDF exploiting InterestGroups flaw
  3. Exploit
    Deliver PDF to victim via phishing or malicious site
  4. Install
    Victim opens PDF in Chrome
  5. C2
    Trigger missing authorization check in InterestGroups API
  6. Execute
    Bypass system access restrictions
  7. Impact
    Achieve high-integrity unauthorized write/modification

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires two conditions to be met simultaneously: (1) the renderer process must already be compromised via a separate, preceding vulnerability - this CVE does not standalone enable renderer compromise; and (2) the victim must interact with a crafted PDF file (UI:R confirmed by CVSS vector). The InterestGroups feature is part of Chrome's Privacy Sandbox and is enabled by default in standard Chrome builds, so no non-default configuration toggle is needed once the renderer is compromised. Limiting factors include: mandatory prior renderer-level code execution, user interaction with a malicious PDF, and Chrome version prior to 152.0.7977.65. Exploitation is not viable against patched instances or where PDF rendering is handled by an external application rather than Chrome's built-in viewer.

Impact

The NVD-assigned CVSS 6.5 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) overstates real-world risk by assigning AC:L and PR:N, but the description explicitly requires a prior renderer-process compromise - a significant precondition that in practice represents a separate vulnerability in a multi-stage chain. This precondition should elevate AC to High, bringing the realistic exploitability considerably lower. Chromium's own security severity rating of Low corroborates this reassessment. EPSS at 0.23% (13th percentile) is consistent with a chained, low-footprint exploitation scenario. No KEV listing and no known POC further reduce urgency. The high integrity impact (I:H) is real once the full chain executes, but the dependency on a preceding renderer exploit means attackers must already have significant capability before this flaw adds value. Priority should be standard patch cadence rather than emergency response, unless the environment involves high-value targets where sophisticated chained Chrome exploits are a realistic threat model.

Exploit ScenarioDerived

An attacker first exploits a separate renderer-process vulnerability to gain code execution within Chrome's sandboxed renderer. They then deliver or redirect the victim to a crafted PDF file - triggering Chrome's internal PDF renderer - which exercises the missing authorization path in the InterestGroups API, allowing the attacker to bypass system access restrictions and achieve high integrity impact beyond the renderer sandbox. No public POC for this specific chained sequence has been identified at time of analysis.

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 27, 2026

Missing authorization in Chrome's InterestGroups API allows a renderer-compromised attacker to bypass system access restrictions via a crafted PDF file. Affected are all Google Chrome versions prior to 152.0.7977.65 across desktop platforms. This is a chained exploit: a prerequisite renderer-process compromise must already exist before the InterestGroups flaw can be leveraged to escalate beyond sandbox constraints and achieve high integrity impact. No public exploit or CISA KEV listing exists; EPSS stands at 0.23% (13th percentile), reflecting very low exploitation probability in the wild.

RemediationAI

Update Google Chrome to version 152.0.7977.65 or later via the built-in update mechanism (Help > About Google Chrome) or enterprise deployment tooling. The vendor-released patch is confirmed through the stable channel update advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Organizations unable to patch immediately should note that exploitation requires a prior renderer-process compromise as a prerequisite; ensuring Chrome's existing sandbox mitigations and Site Isolation are fully enabled (default configuration) reduces the attack surface for the renderer-level precondition. Restricting PDF opening within Chrome via policy (PDF handling set to external viewer) removes the specific delivery vector documented in this CVE, though this may impact productivity. Chromium issue tracker reference: https://issues.chromium.org/issues/533060125.

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

InterestGroups is part of Chrome's Privacy Sandbox initiative, specifically the Protected Audience API (formerly FLEDGE), which manages browser-side interest group data for privacy-preserving ad targeting. The root cause is CWE-862 (Missing Authorization) - the InterestGroups component fails to enforce proper authorization checks when accessed from a compromised renderer context, allowing that renderer to perform operations or access resources beyond its intended privilege boundary. The attack delivery mechanism is a crafted PDF file, meaning the exploit is triggered through Chrome's integrated PDF rendering pipeline. CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms all Chrome desktop builds prior to 152.0.7977.65 are in scope.

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 renderer-process compromise prerequisite, which materially increases exploitation complexity beyond the NVD-assigned AC:L.

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:N/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 27, 2026 - 17:22 NVD
6.5 (MEDIUM)
CVE Published
Aug 25, 2026 - 20:10 cve.org
MEDIUM 6.5
CVE Published
Aug 25, 2026 - 20:10 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Missing authorization in InterestGroups in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted PDF file. (Chromium security severity: Low)

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Ubiquitous
dominant desktop browser, billions of active installations globally
Data Quality
4 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· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
High

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