basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2025-10585
CVE-2025-10585 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-233EPSS 0.05419 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
9 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.05419 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-843 Type Confusion — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-843 · Type ConfusionMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 9 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.