basicsecurity.net
Proof, not just disclosure.
Threats / WebKitGTK / CVE-2019-8720
CVE-2019-8720 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

WebKitGTK vulnerability

WebKitGTK contains a memory corruption vulnerability enabling remote code execution. The flaw has been exploited in the wild.

Verdict

Today item — known-exploited.

A memory corruption defect in WebKitGTK allows unauthenticated attackers to achieve remote code execution through crafted input, with confirmed active exploitation in the wild.

CISA KEV Yes · 2022-05-233EPSS 0.01556 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-05-23).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01556 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: WebKitGTK, WebKitGTK. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
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.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious web content designed to trigger a memory corruption flaw in WebKitGTK's processing logic.
Business
Users browsing untrusted websites or viewing attacker-controlled content face immediate code execution risk.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the exploit payload via a compromised website, email attachment, or embedded frame that the victim's browser processes.
Business
Attack surface spans all applications and services embedding WebKitGTK, multiplying exposure across desktop and embedded systems.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code within the renderer process context, gaining the privileges of the browsing application.
Business
Attackers obtain direct access to user data, credentials, and system resources accessible to the compromised process.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by redhat (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by redhatCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.