Threats / Google / CVE-2025-10585
CVE-2025-10585
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium V8 vulnerability
Google Chromium V8 engine contains a type confusion vulnerability allowing attackers to execute arbitrary code through malicious JavaScript or WebAssembly.
Verdict
Today item — known-exploited.
Type confusion in V8 enables remote code execution when processing specially crafted scripts. Active exploitation in the wild demonstrates immediate threat. Patch urgently for all Chromium-based browsers.
CISA KEV Yes · 2025-09-235EPSS 0.0543 (verify live)6CVSS 8.8 (CISA)4CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-09-23).
Probability (EPSS)
EPSS 0.0543 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Craft malicious JavaScript or WebAssembly that exploits type confusion in V8 object handling.
Business
User systems compromised through browser exploitation, enabling data theft, malware installation, or lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Trigger memory corruption through confused type operations to achieve arbitrary code execution within browser process.
Business
Attackers gain execution context with browser privileges, bypassing sandbox protections and accessing sensitive user data.
3
Lateral reach — past segmentation narrative 3
Attacker
Escalate from browser process to system level through privilege escalation techniques.
Business
Full device compromise possible, affecting enterprise networks and personal systems at scale.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05