Threats / Google / CVE-2025-13223
CVE-2025-13223
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Google Chromium V8 vulnerability
Google Chromium V8 contains a type confusion vulnerability enabling heap corruption. The flaw is tracked as CWE-843 and has been exploited in the wild.
Verdict
Today item — known-exploited.
Type confusion in V8's type system allows attackers to corrupt heap memory, potentially achieving arbitrary code execution within the V8 JavaScript engine context. Active exploitation in the wild indicates practical weaponization.
CISA KEV Yes · 2025-11-194EPSS 0.05026 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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-11-19).
Probability (EPSS)
EPSS 0.05026 — 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 assignment from the public NVD record (may be stale); 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 2 days after 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 that exploits type confusion to trigger heap corruption in V8.
Business
Chromium browser users face remote code execution risk through compromised web content.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Leverage heap corruption to escape V8 sandbox and gain access to host process memory.
Business
Attackers can pivot from browser context to system-level compromise, affecting user data and device security.
3
Lateral reach — past segmentation narrative 3
Attacker
Execute arbitrary code with browser process privileges to install malware or exfiltrate credentials.
Business
Enterprise deployments face data breach and malware distribution risks across user populations.
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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by ChromeCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.