CVE-2019-5786: Google Chrome Blink Use-After-Free
Google Chrome Blink · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-23.
- CVSS v3.1 (CVE record)
- 6.5
- medium
- EPSS (exploit probability, 30 days)
- 61%
- higher than 99.1% of all CVEs
- Added to CISA KEV
- 2022-05-23
- US federal due date 2022-06-13
- Ubuntu priority
- medium
CVE-2019-5786 explained
CVE-2019-5786 is an object lifetime (use-after-free) issue in Blink, the rendering engine in Google Chrome before 72.0.3626.121. A crafted HTML page could cause out of bounds memory access. It is listed in the CISA Known Exploited Vulnerabilities catalog, so it has been exploited in the wild and should be patched promptly.
Impact
A remote attacker can trigger the flaw over the network by getting a user to open a crafted HTML page. No privileges are needed, but user interaction is required. The CVSS vector rates the impact as high for availability and none for confidentiality and integrity. The description says the attacker can potentially perform out of bounds memory access in the browser.
Who is affected
The chromium-browser source package is affected on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. Both have fixed versions in the standard archive: 72.0.3626.121-0ubuntu0.16.04.1 for Ubuntu 16.04 LTS and 72.0.3626.121-0ubuntu0.18.04.1 for Ubuntu 18.04 LTS. Ubuntu 16.04 LTS is end of life. Standard support for Ubuntu 18.04 LTS has ended; further fixes there come only through Ubuntu Pro (ESM).
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 72.0.3626.121
- 72.0.3626.121
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·chromium-browser
Fixed: 72.0.3626.121-0ubuntu0.18.04.1
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 72.0.3626.121-0ubuntu0.16.04.1
What to do
- Update
chromium-browserto72.0.3626.121-0ubuntu0.18.04.1or later on Ubuntu 18.04 LTS. - Update
chromium-browserto72.0.3626.121-0ubuntu0.16.04.1or later on Ubuntu 16.04 LTS. - Close and restart all running browser instances so the patched code is loaded.
- Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release, since it is end of life.
- Consider Ubuntu Pro (ESM) or a release upgrade for Ubuntu 18.04 LTS to keep receiving security fixes.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium-browser with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium-browser"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium-browser"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Partial – limited control or information
Weakness: CWE-416 Use After Free
Questions about CVE-2019-5786
- Is CVE-2019-5786 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-23, with a US federal due date of 2022-06-13. Whether it has been used in ransomware campaigns is unknown.
- Do I need to restart anything after updating?
- Yes. Running browser processes keep using the old code until they are closed and started again. Make sure users restart the browser after the update.
- Can the flaw be triggered without user action?
- No. According to the CVSS rating, user interaction is required: a user must open a crafted HTML page. No privileges are needed and the attack works over the network.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.