Threats / Google / CVE-2026-3910
CVE-2026-3910
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains a buffer overflow vulnerability allowing remote code execution within the sandbox via crafted HTML, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A remote attacker can execute arbitrary code in the V8 sandbox by delivering a malicious HTML page. The vulnerability has been observed in active exploitation. Sandbox escape potential exists but is not confirmed in this advisory.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 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 2026-03-13).
Probability (EPSS)
EPSS 0.02082 — 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-119 Memory Buffer Bounds Error — 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
Craft a malicious HTML page that triggers the buffer overflow in V8 during parsing or execution.
Business
User browsers crash or become unstable, degrading service availability and user experience.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Execute arbitrary code within the V8 sandbox to access sensitive data or establish persistence.
Business
User credentials, browsing history, or cached sensitive information may be compromised.
3
Lateral reach — past segmentation narrative 3
Attacker
Attempt sandbox escape techniques to gain system-level access beyond the browser process.
Business
Full device compromise becomes possible, enabling malware installation or lateral movement.
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