Skip to content
Server Security Center
KEVhigh8.8

CVE-2021-4102: Google Chromium V8 Use-After-Free

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2021-12-15.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
8.5%
higher than 95.1% of all CVEs
Added to CISA KEV
2021-12-15
US federal due date 2021-12-29
Ubuntu priority
medium

CVE-2021-4102 explained

CVE-2021-4102 is a use-after-free flaw in the V8 JavaScript engine of Google Chrome before 96.0.4664.110. A remote attacker could use a crafted HTML page to potentially exploit heap corruption. CISA lists it as known exploited, so affected browsers should be updated promptly.

Impact

An attacker who gets a user to open a crafted HTML page could corrupt heap memory in the browser. This could lead to high impact on confidentiality, integrity and availability. The attack works over the network, needs no privileges and has low complexity, but requires user interaction such as visiting a malicious page. The flaw has been exploited in the wild according to the CISA catalog.

Who is affected

The facts list one affected release. On Ubuntu 18.04 LTS, the source package chromium-browser is fixed in version 97.0.4692.71-0ubuntu0.18.04.1, published in the standard archive. Standard support for Ubuntu 18.04 LTS has ended, and further fixes for that release are only available with Ubuntu Pro (ESM). No other releases or packages are listed in the facts.

Written with AI from the data on this page and checked against it automatically.

Official description

Use after free in V8 in Google Chrome prior to 96.0.4664.110 allowed a remote attacker to potentially exploit heap corruption 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 Chrome
    Affected
    • < 96.0.4664.110
    Fixed in
    • 96.0.4664.110

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.

What to do

  1. Update chromium-browser on Ubuntu 18.04 LTS to 97.0.4692.71-0ubuntu0.18.04.1 or later.
  2. Close and restart all running browser instances so the patched code is loaded.
  3. Plan an upgrade to a supported Ubuntu release, or enable Ubuntu Pro (ESM) for continued fixes on 18.04.
  4. Check other Chromium-based browsers on your systems and update them per vendor instructions.

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" ;; esac

3. 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
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2021-4102

Is CVE-2021-4102 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-12-15, with the required action to apply updates per vendor instructions. Known ransomware use is listed as unknown.
Does updating the package protect me immediately?
Only after the browser is restarted. Running browser processes keep using the old, vulnerable code until they are closed and reopened.
Why does Ubuntu rate this medium when the CVSS severity is high?
Ubuntu assigns its own priority, here medium, separately from the CVSS rating in the CVE record. Both point to a real risk, and the fix should be applied.

Written with AI from the data on this page and checked against it automatically.

References

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.