Skip to main content
ExploitedIn CISA KEVFix available

CVE-2020-6572

Exploitation confirmed. First attested on 2022-01-10 by CISA-ADP, CISA KEV, GCVE · kevintel.

  • Published2021-01-14
  • Fixed in81.0.4044.92
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Use after free in Media in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to execute arbitrary code via a crafted HTML page.

Timeline

dates in UTC
  1. 2021-01-1421:15CVE publishedNVD
  2. 2022-01-10Added to the CISA KEV catalogCISA KEV
  3. 2022-01-10Listed as exploited by GCVEGCVE
  4. 2022-01-10Exploitation first reportedCISA KEV
  5. 2025-02-0415:01SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-6572?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-6572?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Google chrome
BranchAffectedFixed in
81.0< 81.0.4044.9281.0.4044.92

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Chrome, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Google Chrome
    Affected
    • < 81.0.4044.92fixed in 81.0.4044.92custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2021-01-14

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • chromiumDebian:14all versions · fixed in 81.0.4044.92-1
  • chromiumDebian:13all versions · fixed in 81.0.4044.92-1
  • chromiumDebian:12all versions · fixed in 81.0.4044.92-1
  • chromium-browserUbuntu:18.04:LTSall versions · fixed in 89.0.4389.82-0ubuntu0.18.04.1
  • chromium-browserUbuntu:16.04:LTSall versions · fixed in 89.0.4389.82-0ubuntu0.16.04.1

Full record on NVD

Fix

  1. Update Google chrome to 81.0.4044.92
  2. CISA’s required action: Apply updates per vendor instructions.due 2022-07-10

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2022-01-10
Patch Due Date
2022-07-10
Ransomware Use
Unknown
Required Action
Apply updates per vendor instructions.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2021-01-14
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-48wj-mfx4-4qc2

Frequently asked questions

What is CVE-2020-6572?

Use after free in Media in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to execute arbitrary code via a crafted HTML page.

Is CVE-2020-6572 actively exploited?

Yes. CVE-2020-6572 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2022-07-10.

What is the CVSS score for CVE-2020-6572?

CVE-2020-6572 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running chromium? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record