CVE-2019-5786
Google Chrome Blink Use-After-Free
- Published27 Jun 2019
- Added to CISA KEV23 May 2022
- Remediation due13 Jun 2022
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2019-5786 being actively exploited?
Yes. CVE-2019-5786 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 23 May 2022.
How severe is CVE-2019-5786?
CVE-2019-5786 has a CVSS 3.1 base score of 6.5, rated medium. EPSS estimates a 61.1% probability of exploitation.
Which products are affected by CVE-2019-5786?
Affected products include Google Chrome.
How do I fix CVE-2019-5786?
Upgrade affected software to a fixed version, for example Google Chrome 72.0.3626.121 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2019-5786 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.