Secuno
ENNL
Book demo

CVE-2026-14086

Google Chrome remote code execution

8.8 HIGHEPSS 0.41%
  1. Published30 Jun 2026

Description

Insufficient policy enforcement in HID in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Low)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Google Chrome< 150.0.7871.47

Remediation

Fixed in
Google Chrome≥ 150.0.7871.47

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-131388.6
Client-Side Enforcement of Server-Side Security vulnerability in Divasoft Software and…
CVE-2026-595049.1
: Client-Side Enforcement of Server-Side Security vulnerability in Priority Portal…
CVE-2026-728679.9
Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.3 until…
CVE-2026-6481310.0
In JetBrains IntelliJ IDEA before 2026.2 unauthorized settings modification was…
CVE-2026-464858.2
Dashy is a self-hostable personal dashboard. Prior to 4.0.8, Dashy deployments using…
CVE-2026-141099.6
Insufficient policy enforcement in Mojo in Google Chrome prior to 150.0.7871.47 allowed…

Frequently asked

Is CVE-2026-14086 being actively exploited?

CVE-2026-14086 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.41%.

How severe is CVE-2026-14086?

CVE-2026-14086 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2026-14086?

Affected products include Google Chrome.

How do I fix CVE-2026-14086?

Upgrade affected software to a fixed version, for example Google Chrome 150.0.7871.47 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-14086 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.