IRONSMITHINTEL
MEDIUMCVSS6.5
|
Actively Exploited
|CISA KEV|CVE-2019-5786|Auth: none — unauthenticated|Reboot: required|Manual only

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.

Published Jun 27, 2019 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve partial data exposure, complete denial of service or system unavailability. Federal agencies are required to remediate by 2022-06-13 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Use After Free (CWE-416) vulnerability in Google Chrome Blink. 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. Exploitation requires remote network access, low attack complexity, no authentication required, and user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

Endpoint Administrators
IT Security
Running chrome: v < 72.0.3626.121
Real-world incidentsWhat we've seen

Active exploitation documented in the wild. Threat-research write-up: https://crbug.com/936448

How to patch

Manual remediation steps

Apply the Vendor Patch

This vulnerability is in the CISA Known Exploited Vulnerabilities catalog — apply the vendor's security update as soon as possible.

CISA required action: Apply updates per vendor instructions.

References

    1
    Vendor advisory: https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop.html
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2019-5786
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-5786
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.