CVE-2019-5786
Published: May 23, 2022
Official Description
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
CISA KEV Advisory
Google Chrome Blink Use-After-Free Vulnerability
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
Apply updates per vendor instructions.
Risk Analysis
This vulnerability in Google Chrome's Blink engine is a heap use-after-free flaw, allowing an attacker to potentially perform out-of-bounds memory access via a crafted HTML page. With a high EPSS score of 0.89450 and its presence in CISA's KEV, this flaw is actively exploited and poses a significant risk to browser security.
Active exploitation of this vulnerability has been observed in the wild and it is listed in CISA's KEV, indicating confirmed real-world attacks. The flaw is remotely exploitable, typically through malicious websites.
Users should update Google Chrome to the latest patched version immediately. Ensure all web browsers are kept up-to-date to protect against such memory corruption vulnerabilities.
Technical Analysis
CVE-2019-5786 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2019-5786 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2019-5786 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1