Skip to main content

Google Chrome CVE-2026-14041

| EUVDEUVD-2026-40728 HIGH
Client-Side Enforcement of Server-Side Security (CWE-602)
2026-06-30 chrome-cve-admin@google.com GHSA-499r-fh8q-qcfc
High
Disputed · 8.8 Vendor: google
View

Attack ChainAIDerived

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

  1. Access
    Lure victim to crafted HTML page
  2. Delivery
    Page invokes Web Serial API
  3. Exploit
    Bypass insufficient Serial policy enforcement
  4. Execution
    Escalate privileges in browser context
  5. Impact
    Access resources beyond intended permission

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V4 - API and Web Service Server-side security enforcement
Exploitation Conditions

Exploitation requires the victim to open a crafted HTML page in a Chrome build prior to 150.0.7871.47 - user interaction is mandatory (CVSS UI:R), so this is not a drive-by against a fully passive user in the strictest sense but needs page navigation. The affected surface is specifically the Serial (Web Serial API) component and its policy enforcement, so exposure is limited to environments where that browser feature/code path is reachable; enterprises that disable Web Serial via policy remove the affected surface. No authentication is required (PR:N), and the attack is remote/network-delivered (AV:N) with low complexity (AC:L). Limiting factors: mandatory user interaction, Chromium's own Low severity rating, and the niche nature of the Serial API reduce realistic exploitability well below what the 8.8 base score alone suggests.

Impact

The signals conflict and must be weighed rather than taken at face value. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 8.8) implies a network-reachable, low-complexity, unauthenticated attack needing only user interaction (visiting a page) with full CIA impact - which would normally be a priority. However, Chromium's own severity rating is Low, and the EPSS probability is only 0.17% (7th percentile), both of which argue this is not high real-world risk. It is not in CISA KEV (no confirmed active exploitation) and no public POC is identified. Web Serial is not enabled/used on most sites and typically requires an explicit permission grant, which likely explains the gap between the high CVSS and Chromium's Low rating. Bottom line: patch in the normal Chrome auto-update cycle; this is not an emergency despite the 8.8 number. The CVSS 'C:H/I:H/A:H' rating appears aggressive relative to a policy-enforcement bug in a niche API - verify scope with the vendor advisory before treating it as full-system compromise.

Exploit ScenarioDerived

An attacker hosts or compromises a website and entices a victim to open it in a vulnerable Chrome build; the crafted HTML page abuses the insufficiently enforced Serial policy to gain privileges it should not have. Because the CVSS vector requires user interaction (UI:R) but no prior authentication (PR:N), the only prerequisite is getting the target to visit the page. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 – Jul 01, 2026

Privilege escalation in Google Chrome desktop before 150.0.7871.47 stems from insufficient policy enforcement in the Serial (Web Serial API) component, allowing a remote attacker who lures a victim to a crafted HTML page to escalate privileges within the browser. Note the signal conflict: NVD scores this 8.8 (High) with high confidentiality/integrity/availability impact, yet Chromium's own triage rates the security severity as Low. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is very low at 0.17% (7th percentile).

RemediationAI

Vendor-released patch: Chrome 150.0.7871.47 - upgrade to this Stable release or later, which for most users happens automatically via Chrome's background updater; confirm the version under Settings > About Google Chrome and relaunch to apply. Reference the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html for the full stable-channel bulletin. In managed/enterprise fleets, push the update through your Chrome update policy or software distribution system and verify the reported version across endpoints. As an interim compensating control until updated, restrict the Web Serial API via enterprise policy (for example the DefaultSerialGuardSetting / SerialAskForUrls-style device policies) to block or gate serial-port access, which closes the exposed feature at the cost of breaking legitimate WebSerial-based tools (hardware programmers, some web-based device configurators). Chromium-based browsers should receive their vendor's equivalent update.

Affected VersionsENISA

Chrome 150.0.7871.47 <150.0.7871.47

Affected Packages

euvd chrome fix: 150.0.7871.47

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 flaw lives in Chrome's Serial subsystem, which implements the Web Serial API - a browser capability that lets web pages request access to local serial (COM/tty) ports after a user permission prompt. The root cause maps to CWE-602 (Client-Side Enforcement of Server-Side Security), a class of bug where a security decision or policy that should be strictly enforced is instead applied too loosely or on the wrong side of a trust boundary, letting a page bypass the intended permission/policy gate. In practice, insufficient policy enforcement in this component can let a page reach serial-related privileges it should not have, expanding the attack surface exposed to untrusted web content. Affected CPE-wise: Google Chrome desktop builds prior to 150.0.7871.47; the underlying Chromium engine means Chromium-derived browsers may share the code path.

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 (Low–High)
Vendor (google) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 5.4 MEDIUM

Remote crafted page with required user interaction (UI:R), no auth (PR:N); impact lowered to C:L/I:L/A:N since a Serial policy-enforcement bypass is niche and Chromium rates it Low, not full-system CIA.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
SUSE HIGH
Red Hat 4.3 LOW

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: google

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

Lifecycle Timeline

3
CVSS changed
Jul 01, 2026 - 15:22 NVD
8.8 (HIGH)
CVE Published
Jun 30, 2026 - 23:17 cve.org
HIGH 8.8
CVE Published
Jun 30, 2026 - 23:17 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient policy enforcement in Serial in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)

Executive ViewAI

Why It Matters

Google Chrome before version 150.0.7871.47 contains a privilege escalation vulnerability that could allow attackers to escape browser protections and execute arbitrary code. Despite a High CVSS score, exploitation is considered unlikely-no public exploits exist, the vulnerability is not actively exploited, and the vendor rates it as Low severity. Patch deployment should proceed on the organization's standard security update schedule.

Business Impact: Medium
Compensating Controls

Apply vendor patch: Chrome 150.0.7871.47 or later

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Ubiquitous
Google Chrome is the most widely deployed desktop web browser
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

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

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Package Hub 15 SP7 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