CVE WatchJul 14, 2026

CVE-2025-10585

Google Chromium V8 Type Confusion Vulnerability

CVSS

9.8

Critical

EPSS

5.4%

p92

KEV

YES

Sep 23, 2025

Exploit Today

0-100

Published: Sep 24, 2025 · Last modified: Jul 14, 2026 · CWE-843

EPSS · 30d

5.4%EPSS · 30 days5.4%

2026-08-022026-08-31

KEV catalog record

Product

Google / Chromium V8

Vulnerability

Google Chromium V8 Type Confusion Vulnerability

Added to KEV

Sep 23, 2025

Remediate by

Oct 14, 2025

Known ransomware use

Summary description

Google Chromium contains a type confusion vulnerability in the V8 JavaScript and WebAssembly engine.

Required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Notes

https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_17.html ; https://nvd.nist.gov/vuln/detail/CVE-2025-10585

Technical description

Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Official references

Related CVEs

CVECVSSEPSSKEVRExploitTitleMod.

CVE-2026-729848.8 HIG

36.9%

——11Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.2d CVE-2026-19315—

38.0%

——11A type confusion vulnerability in the iked process of WatchGuard Fireware OS allows a remote unauthenticated attacker to execute arbitrary code by sending specially crafted network traffic.2d CVE-2026-593043.1 LOW

4.5%

——1Improper caching of the original content type in Spring Cloud Stream Avro. Spring Cloud Stream 5.0.0 - 5.0.2 Spring Cloud Stream 4.3.0 - 4.3.3 Spring Cloud Stream 4.2.0 - 4.2.63d CVE-2026-80183—

13.1%

——4In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under any domain by passing a domain ID as scope.project.id with include_subtree to the GET /v3/role_assignments endpoint. The domain's project record has domain_id=null, causing the policy domain_id check to pass for any caller. With include_names, the response discloses the names and home-domain IDs of every user, group, project, and role involved. The literal "default" domain ID works against any deployment created with keystone-manage bootstrap. An attacker can harvest domain IDs from the response and repeat the query to map role assignments across the entire cloud. This is caused by misuse of "None" in list_role_assignments_for_tree.4d CVE-2026-801855.7 MED

14.5%

——4BlueZ sdp-xml.c type confusion via RegisterProfile(ServiceRecord) can crash bluetoothd (local DoS): a crafted nested ServiceRecord can corrupt the SDP XML parser stack so scalar union data is treated as a sequence pointer, allowing a local caller to crash bluetoothd.3d CVE-2026-792368.8 HIG

41.4%

——12Type confusion in V8 in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)4d