CVE-2019-5786

Exp

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: 2019-06-27 Last update: 2025-10-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-5786 is rated Critical Active Threat (86.4/100): CVSS Medium severity, with high exploitation likelihood (EPSS 89.94%, 100th percentile). CISA KEV confirms active exploitation (added 2022-05-23) affecting Google / Chrome Blink. a weakness (CWE-416) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2019-5786

Name: Google Chrome Blink Use-After-Free Vulnerability · CISA KEV detail

Exploit added: 2022-05-23

Action due: 2022-06-13

Required action: Apply updates per vendor instructions.

Public exploit references (Exploit-DB) for CVE-2019-5786

EDB-ID Source Kind Published Link
46812 exploit_db edb 2019-05-08 Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-5786

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-20 89.38% 89.94% +0.56%
2 2026-04-27 89.48% 89.38% -0.10%
3 2026-04-21 — 89.48% —

Full EPSS history (46 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-5786

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-5786

GitHub Security Advisory for CVE-2019-5786

OS Trackers for CVE-2019-5786

vendor priority summary link
alpine — CVE-2019-5786: 1 source package rows (chromium); 7 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2019-5786
debian not yet assigned CVE-2019-5786 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-5786
gentoo high CVE-2019-5786: 1 GLSA(s) (201903-23), 1 atom(s) (www-client/chromium); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-5786
redhat high — https://access.redhat.com/security/cve/CVE-2019-5786
ubuntu medium CVE-2019-5786 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (bionic, cosmic, trusty, upstream, xenial): released 4, DNE 1. https://ubuntu.com/security/CVE-2019-5786

Affected software / configurations for CVE-2019-5786

Vendor Product Version Raw CPE
google chrome < 72.0.3626.121 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2019-5786

cvelogic Threat Intelligence