Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2021-21166: Google Chrome Audio Data Race Leading to Renderer Code Execution

Published Mar 9, 2021 · Updated 20 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS24.0%98th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendors
GoogleDebian ProjectFedora Project
IdentifiersCVE-2021-21166CWE-362 · Concurrent Execution using Shared…

CVE-2021-21166 is a data race in the audio component of Google Chrome versions before 89.0.4389.72. A remote attacker can use a crafted HTML page to trigger heap corruption, potentially enabling arbitrary code execution in the browser renderer. The vulnerability was exploited as a zero-day in Candiru-linked targeted attacks using single-use links. A related flaw affecting WebKit was patched separately as CVE-2021-1844.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the Chrome renderer through heap corruption and arbitrary code execution. This vulnerability alone does not establish a browser sandbox escape, operating-system privilege escalation, or unrestricted host compromise. It was used in targeted exploitation associated with Candiru spyware operations.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, reduce exposure by restricting use of untrusted or unsolicited links and web content, especially in high-risk targeted environments. Employ browser sandboxing, exploit mitigation controls, rapid browser restart/update policies, and application isolation for sensitive users. Network and endpoint monitoring for suspicious browser exploitation chains can help detect attempted abuse, but mitigation is not a substitute for installing the vendor fix.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 89.0.4389.72 or later, preferably the latest supported release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2021-21166 exploited in the wild?
Yes. As of Oct 28, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2021-21166?
As of Oct 28, 2026, Mallory has found no public exploit for CVE-2021-21166.
Is there a patch for CVE-2021-21166?
Upgrade Google Chrome to version 89.0.4389.72 or later, preferably the latest supported release.
What products are affected by CVE-2021-21166?
Google Chrome, Debian Project Debian Linux, and Fedora Project Fedora.
How severe is CVE-2021-21166?
CVE-2021-21166 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 24.0% (98th percentile) as of Oct 28, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.