How severe is CVE-2019-5786?

CVE-2019-5786 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-5786?

CVE-2019-5786 affects the following packages: puppeteer (npm). Ecosystems affected: npm.

How do I fix CVE-2019-5786?

Update puppeteer to version 1.13.0 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2019-5786 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2019-5786, including 1 documented proof-of-concept exploit on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-5786?

CVE-2019-5786 has an EPSS (Exploit Prediction Scoring System) score of 89.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-5786 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-5786 (Google Chrome Blink Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-23. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-13. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-5786?

CVE-2019-5786 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-5786 published, and has it been updated?

CVE-2019-5786 was published on June 27, 2019 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-05-23 — agencies required to remediate by 2022-06-13

📦 npm

CVE-2019-5786

MEDIUM

Use-After-Free in puppeteer

Also known asGHSA-c2gp-86p4-5935

Published

Jun 27, 2019

Updated

Mar 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

89.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦puppeteer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`puppeteer`	all versions	1.13.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46812remotewindows_x86✓ Verified

Google Chrome 72.0.3626.119 - 'FileReader' Use-After-Free (Metasploit)

by Metasploit · May 8, 2019

Exploit-DB Source

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2019-5786 in your stack?

O3 detects CVE-2019-5786 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works