CVE Intelligence
CISA KEV Medium Memory corruption exploit reference

CVE-2019-5786 — Google Chrome Blink Use-After-Free Vulnerability

Object lifetime issue in Blink in Google Chrome prior to 72.0.3626.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.

Published Jun 27, 2019 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: Chrome

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · May 23, 2022 Metasploit modules · 1Exploit-DB · 1
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (metasploit, exploitdb)+20
  • EPSS 61.1% (30-day exploitation probability)+15
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 23, 2022
EPSS FIRST
61.09%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Google
Chrome and 1 more
CVSS base
6.5
Medium · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm Puppeteer: fixed in version 1.13.0 — github.com (GitHub Security Advisories)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 13, 2022 — passed 1585 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Google Chrome, Npm Puppeteer).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  6. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  7. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Google Chrome < 72.0.3626.121 Vulnerable CVE Program (cve.org) e CISA ADP
Google Chrome < 72.0.3626.121 Vulnerable NIST National Vulnerability Database
Npm Puppeteer < 1.13.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium 2.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — CISA-ADP via CVE Program (cve.org) e CISA ADP
6.5 CVSS 3.0 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-416 · Use After Free

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 23, 2022
Federal deadline
Jun 13, 2022
passed 1585 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules
Exploit-DB

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 61.09%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
  • Hunt retroactively in logs from before May 23, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Analysis and videos

CVE-2019-5786: Google Chrome Blink Use-After-Free Vulnerability
CVE-2019-5786 is a use-after-free flaw (CWE-416) in the Blink rendering engine of Google Chrome before 72.0.3626.121, which a remote attacker could potentially trigger with a crafted HTML page. CISA lists it in the Known Exploited Vulnerabilities catalog, and the record also lists npm Puppeteer below 1.13.0 as affected. Updating Chrome and Puppeteer is the main defensive step.

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · npm/puppeteer
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · google/chrome
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · google/chrome
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 6.5
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    May 22, 2022 · CISA
  • 2019
  • CVE published
    Jun 27, 2019 · Chrome

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Google
every CVE for this vendor
2022-05
what else CISA listed that month
Memory corruption
same class
CWE-416
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-110172 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • CVE-2026-110170 Use after free in Bindings in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • CVE-2026-110171 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • CVE-2026-110168 Use after free in V8 in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to execute... 1d
  • CVE-2026-110163 Use after free in DOM in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • CVE-2026-110162 Use after free in Desktop in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-5786 is "Google Chrome Blink Use-After-Free Vulnerability", rated Medium. It affects Chrome (Google); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 6.5 describes technical severity. EPSS 61.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.