Threats / Google / CVE-2022-3723
CVE-2022-3723
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Type confusion vulnerability in Google Chromium V8 engine allows remote attackers to exploit heap corruption through crafted HTML, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A remote attacker can craft malicious HTML to trigger type confusion in V8, potentially achieving heap corruption and code execution in any browser using the affected Chromium engine. Active exploitation in the wild confirms practical threat.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 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 2022-10-28).
Probability (EPSS)
EPSS 0.0675 — 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-122 Heap-based Buffer Overflow, 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 exploiting type confusion in V8's object handling.
Business
User visits attacker-controlled or compromised website, exposing browser to code execution.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger heap corruption through the type confusion, gaining memory control within the V8 process.
Business
Attacker achieves arbitrary code execution in the browser's security context with user privileges.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute malicious code to steal credentials, install malware, or pivot to the host system.
Business
User data, credentials, and system integrity are compromised; potential lateral movement to enterprise networks.
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