Skip to main content

Google Chrome CVE-2026-78897

| EUVDEUVD-2026-66033 MEDIUM
Missing Authorization (CWE-862)
2026-08-25 Chrome GHSA-46ww-4fff-23g3
Medium
Disputed · 6.5 Vendor: Chrome
View

Attack ChainAIDerived

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

  1. Access
    Attacker crafts malicious Chrome extension
  2. Delivery
    Distribute via phishing or social media
  3. Exploit
    Victim installs extension (social engineering)
  4. Execution
    Extension invokes BrowserTag without authorization check
  5. Persist
    Sensitive browser state returned to extension
  6. Impact
    Attacker exfiltrates data

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 that the victim be running Google Chrome prior to 152.0.7977.65 AND be socially engineered into installing a crafted Chrome extension - this is the non-negotiable prerequisite encoded in the UI:R CVSS metric. The attack is network-delivered (AV:N) and requires no prior authentication to Chrome or the target system (PR:N), but the social engineering step is a concrete limiting factor: the extension must be installed with user consent or via a compromised extension distribution channel. Exploitation is further limited because the impact is confidentiality-only (no code execution, no integrity impact) and is not automatable per SSVC assessment. Defenders on managed devices who enforce extension allowlisting policies are not realistically exposed.

Impact

The CVSS 3.1 base score of 6.5 (Medium) reflects a network-reachable, low-complexity attack with no privilege requirement but mandatory user interaction (UI:R) and confidentiality-only impact (C:H/I:N/A:N). Real-world risk is substantially lower than the base score implies. EPSS at 0.23% places this in the 13th percentile - well below exploitation thresholds typically associated with commodity attacks. SSVC signals reinforce this: exploitation is 'none,' the attack is not automatable, and technical impact is only 'partial.' The social engineering dependency (convincing a user to install a crafted extension) introduces a meaningful friction barrier. Chromium itself rates severity as 'Low.' No KEV listing and no public POC have been identified. The primary gap between raw CVSS and real-world risk is the non-trivial social engineering step required; this is not a drive-by or unauthenticated remote exploit.

Exploit ScenarioDerived

An attacker crafts a malicious Chrome extension and distributes it via a phishing page, fake software bundle, or social media, persuading a target to install it manually. Once installed, the extension exploits the missing BrowserTag authorization check to query sensitive browser state - such as tab metadata, browsing context identifiers, or cross-origin signals - that it would not normally be permitted to access. No public exploit code has been identified at time of analysis, making mass exploitation unlikely in the near term.

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

Missing authorization in the BrowserTag component of Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive information by distributing a crafted Chrome extension via social engineering. The flaw bypasses authorization checks within BrowserTag, allowing the malicious extension to access data it should not be permitted to read. No active exploitation has been identified (CISA KEV absent), EPSS sits at 0.23% (13th percentile), and Chromium's own severity classification is 'Low' - all consistent with the UI:R prerequisite of tricking a user into installing a hostile extension.

RemediationAI

Update Google Chrome to version 152.0.7977.65 or later, available via Chrome's built-in auto-update mechanism or the vendor advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Organizations managing Chrome via policy (Google Admin Console, Intune, or similar) should push the update and verify version compliance. As a compensating control prior to patching, enforce enterprise extension allowlisting (ExtensionInstallAllowlist policy) to prevent installation of unapproved extensions - this directly eliminates the social engineering vector since the crafted extension cannot be installed without policy approval. Note that extension allowlisting may disrupt workflows for users who install personal extensions; evaluate against operational requirements before deployment.

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

BrowserTag is an internal Chrome browser component involved in extension or tab-tagging logic. The root cause is CWE-862 (Missing Authorization) - the component fails to enforce access controls before exposing sensitive data to a requesting extension context. The affected product is identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome desktop builds prior to version 152.0.7977.65. Because Chrome extensions operate in a privileged but sandboxed context, an extension that bypasses BrowserTag authorization can read browser state (e.g., browsing context metadata, tab information, or cross-origin signals) without the corresponding manifest permission grant.

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:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-delivered via extension install (AV:N/PR:N), requires active user consent (UI:R), confidentiality-only impact with no integrity or availability effect.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/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
High
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Aug 26, 2026 - 19: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 BrowserTag in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted Chrome extension. (Chromium security severity: Low)

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Ubiquitous
dominant desktop browser, installed across virtually all enterprise and consumer environments
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