Threats / Google / CVE-2019-13720
CVE-2019-13720
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chrome WebAudio vulnerability
Google Chrome WebAudio contains a use-after-free vulnerability allowing remote attackers to exploit heap corruption through crafted HTML pages.
Verdict
Today item — known-exploited.
A use-after-free in Chrome WebAudio enables remote code execution via malicious web content. The high EPSS score and active exploitation in the wild indicate immediate risk to users visiting untrusted sites.
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 2022-05-23).
Probability (EPSS)
EPSS 0.72977 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chrome WebAudio. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-416 Use After Free — 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 improper memory handling in the WebAudio API.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution within the browser process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit through drive-by download, phishing, or ad networks to maximize reach.
Business
Chrome users lack protection without patching, exposing credentials, session tokens, and local data to compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence or pivot to system-level compromise once code execution is achieved.
Business
Incident response costs, user trust erosion, and potential regulatory exposure from data breaches escalate rapidly.
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