Threats / Google / CVE-2023-4762
CVE-2023-4762
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains a type confusion vulnerability allowing remote code execution through crafted HTML pages, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A type confusion flaw in V8 enables remote attackers to execute arbitrary code by delivering malicious HTML. The vulnerability is actively exploited in the wild, posing immediate risk to users of Chromium-based browsers.
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
5 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 2024-02-06).
Probability (EPSS)
EPSS 0.37987 — 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
Users visiting attacker-controlled or compromised websites face arbitrary code execution on their systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the exploit page on a website or distribute it via phishing to maximize victim reach.
Business
Browser vendors face increased support burden and reputational damage from widespread exploitation.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute malware, steal credentials, or establish persistence on compromised machines.
Business
Enterprises experience data breaches, credential compromise, and potential lateral movement within 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