CVE-2026-14086
CVE-2026-14086 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-602.
Key facts
- Severity: High (CVSS 3.x base score 8.8)
- EPSS exploit prediction: 0% (22nd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-602
- Affected product: Google Chrome
- Published:
- Last modified:
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)
Frequently asked questions
- What is CVE-2026-14086?
- 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)
- How severe is CVE-2026-14086?
- CVE-2026-14086 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-14086 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-14086?
- CVE-2026-14086 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-14086?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-14086 published?
- CVE-2026-14086 was published on 2026-06-30 and last updated on 2026-07-02.
References
- https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html
- https://issues.chromium.org/issues/513169718
Affected products (1)
- cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
More vulnerabilities in Google Chrome
- CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
- CVE-2015-8548 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow…
- CVE-2015-6791 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.80 allow attackers to cause a denial of service…
- CVE-2015-6788 — Critical (CVSS 10.0): The ObjectBackedNativeHandler class in extensions/renderer/object_backed_native_handler.cc in the extensions subsystem…
- CVE-2015-8480 — Critical (CVSS 10.0): The VideoFramePool::PoolImpl::CreateFrame function in media/base/video_frame_pool.cc in Google Chrome before…
- CVE-2015-6787 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.73 allow attackers to cause a denial of service…
All CVEs affecting Google Chrome →
Other CWE-602 vulnerabilities
- CVE-2026-42160 — Critical (CVSS 10.0): Data Space Portal is an open-source Software as a Service (SaaS) solution designed to streamline Dataspace management.…
- CVE-2025-33025 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
- CVE-2025-33024 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
- CVE-2025-32469 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
- CVE-2026-30783 — Critical (CVSS 9.8): A vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android, WebClient…
- CVE-2026-23478 — Critical (CVSS 9.8): Cal.com is open-source scheduling software. From 3.1.6 to before 6.0.7, there is a vulnerability in a custom NextAuth…