+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2019-5786 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.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 23 May 2022.
  • Rated Medium severity (CVSS 6.5, scored by CISA).
  • It has been in the catalogue for 1,628 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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 Versions

ProductVersions
Google Chromeunspecified to before 72.0.3626.121

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Google Chrome Blink. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsCyber Essentials requires high and critical updates (CVSS 7.0 or above) within 14 days of release. Treat any exploited flaw the same way.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 13 Jun 2022 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Google Flaws

Get alerts for GoogleWe email you when a new Google vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-111497Google Brotli Unchecked Return Value VulnerabilityAdded 27 Oct 2026CVE-2026-58704Google Pixel Improper Authorization VulnerabilityAdded 16 Sep 2026CVE-2026-87491Google Chromium V8 Out of Bounds Write VulnerabilityAdded 9 Sep 2026CVE-2026-85046Google Chromium V8 Type Confusion VulnerabilityAdded 4 Sep 2026CVE-2026-11645Google Chromium V8 Out-of-Bounds Read and Write VulnerabilityAdded 9 Jun 2026CVE-2026-5281Google Dawn Use-After-Free VulnerabilityAdded 1 Apr 2026

All 76 exploited Google vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2019-5786 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2019-5786
  3. CVE record: CVE-2019-5786
  4. FIRST EPSS
  5. crbug.com/936448
  6. chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop.html