Threats / Google / CVE-2019-5786
CVE-2019-5786
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chrome Blink vulnerability
Google Chrome Blink contains a heap use-after-free vulnerability allowing attackers to perform out-of-bounds memory access through crafted HTML pages.
Verdict
Today item — known-exploited.
A use-after-free flaw in Chrome's Blink rendering engine enables remote code execution when users visit malicious web content. The high EPSS score and active exploitation in the wild indicate immediate risk to browser users.
CISA KEV Yes · 2022-05-234EPSS 0.61537 (verify live)5Exploit Public PoC6CVSS 6.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3
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
2 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.61537 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) · Affected: Google, Chrome Blink. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1061 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 memory corruption in Blink's heap management.
Business
Users visiting untrusted websites face arbitrary code execution within browser context, compromising system security.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the use-after-free to read or write sensitive memory regions containing user data or credentials.
Business
Confidential information stored in browser memory becomes accessible to attackers, enabling credential theft and data exfiltration.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage out-of-bounds access to escape the browser sandbox and gain host system privileges.
Business
Full device compromise becomes possible, allowing attackers to install malware, steal files, or establish persistent access.
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