CVE Tools
Track your stack

CVE-2021-21220

Exploited in the wild. In CISA KEV since 2021‑11‑03. Fixed in 89.0.4389.128.

CVSS 3.18.8HighEPSS percentile99th70% chance in 30 daysCISA KEVListedsince 2021-11-03, due 2021-11-17
Public exploit: 3 sourcesFix89.0.4389.128Upgrade to this build

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Google ChromeAffected: ≥ unspecified, < 89.0.4389.128Upgrade to: 89.0.4389.128Stated by: CVE record
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 9Upgrade to: not statedStated by: BDU
  • ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.6 «Смоленск»Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

Coverage timeline

0 publishers

  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

Insufficient validation of untrusted input in V8 in Google Chrome prior to 89.0.4389.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2021-11-03.

US federal agencies must remediate by 2021-11-17.

Apply updates per vendor instructions.
Public exploits

3 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

70% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 133 days before any public exploit.

  1. OpenVAS check added
  2. EPSS band changecritical → high
  3. Public exploit / PoCsource: other
  4. Patch availablerecord updated
  5. Added to CISA KEV
  6. Publishedweakness classified, att&ck mapped

Affected products

And 2 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 13 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Chrome, not every advisory. This one: actively exploited.