CVE-2025-10585 · Published 24 Sep 2025
Google Chromium V8
On CISA's KEV list; 4 public exploits.
Google Chromium contains a type confusion vulnerability in the V8 JavaScript and WebAssembly engine.
CISA required action (federal due date 14 Oct 2025): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 23 Sep 2025, due 14 Oct 2025
- EPSS, 30-day forecast
- 9.0%, 95th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 19 Sep 2025 to today
- First PoC
- KEV+4 d
- Disclosed+1 d
4 days from the first proof of concept to the KEV listing
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 4 known · links only
GitHub PoCs 4Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars4
- AdityaBhatt3010/CVE-2025-10585-The-Chrome-V8-Zero-Day13 stars
Trust ok 85 · 1 flag
- no source (no_source)
Google patched CVE-2025-10585, a Chrome V8 zero-day under active exploitation — here’s what it is, why it matters, and how to stay safe.
created 19 Sep 2025
- dexteon/cve-2025-10585-pocTrust ok 1000 stars
Research notes for cve-2025-10585-poc
created 12 Nov 2026
- callinston/CVE-2025-10585Not checked
first seen by skopnix 18 Oct 2026
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.