Threats / Google / CVE-2022-4262
CVE-2022-4262
· 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 pages, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A remote attacker can trigger type confusion in V8's memory management by delivering a malicious HTML page, potentially achieving code execution or information disclosure through heap corruption.
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
7 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-12-05).
Probability (EPSS)
EPSS 0.16109 — 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 an HTML page that triggers type confusion in V8's type system, causing the engine to misinterpret object types.
Business
User's browser crashes or becomes unstable, disrupting productivity and user trust in the platform.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the resulting heap corruption to read or write arbitrary memory locations within the browser process.
Business
Sensitive user data including credentials, session tokens, or cached information becomes accessible to attackers.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the memory corruption to achieve remote code execution within the browser's security context.
Business
Attacker gains ability to execute arbitrary code on user systems, potentially leading to malware installation or system compromise.
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