Threats / Google / CVE-2025-6554
CVE-2025-6554
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 type confusion vulnerability allows remote attackers to perform arbitrary read/write operations through crafted HTML pages, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
Type confusion in V8 engine enables memory corruption attacks via malicious web content. Exploitation requires user interaction but poses significant risk to confidentiality and integrity of browser processes and user data.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
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-07-02).
Probability (EPSS)
EPSS 0.06564 — 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.
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.
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
I craft a malicious HTML page that triggers type confusion in the V8 JavaScript engine.
Business
User visits attacker-controlled or compromised website, exposing browser to code execution risk.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the type confusion to corrupt memory and gain arbitrary read/write capabilities within the browser process.
Business
Attacker gains ability to exfiltrate sensitive data from browser memory or modify application behavior.
3
Lateral reach — past segmentation narrative 3
Attacker
I use read/write primitives to bypass security mechanisms and achieve code execution with browser privileges.
Business
Browser compromise leads to potential malware installation, credential theft, or lateral movement to host system.
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