ChromeWeb browser · Google

CVE-2021-21124

CRITICAL · 9.6 CVSS v3.1 Published 2021-02-09
Fix available
A fix is available. Upgrade to 88.0.705.50 / 88.0.4324.96 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Potential user after free in Speech Recognizer in Google Chrome on Android prior to 88.0.4324.96 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability in the Speech Recognizer component of Google Chrome on Android allows a remote attacker to exploit via a crafted HTML page, potentially enabling sandbox escape and arbitrary code execution.

MitigationUpdate Google Chrome on Android to version 88.0.4324.96 or later to patch the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 88.0.4324.96
Edge ChromiumWeb browser
Affected:< 88.0.705.50

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome Android version
    Open Chrome on the Android device, tap the three-dot menu, go to Settings > About Chrome, and note the version number displayed.
    Affected if Version is below 88.0.4324.96
  2. Check Microsoft Edge Chromium Android version
    Open Edge on the Android device, tap the three-dot menu, go to Settings > About Microsoft Edge, and note the version number displayed.
    Affected if Version is below 88.0.705.50
  3. Verify Speech Recognizer accessibility
    Confirm that the browser can access the Speech Recognition API by visiting a webpage that uses the Web Speech API, or check if any installed applications use Chrome's built-in speech recognition features.
    Affected if Speech Recognizer component is accessible or being used while the browser version is vulnerable
  4. Confirm Android platform and browser combination
    Identify that the affected Chrome/Edge instance is running on Android (not desktop), as this vulnerability specifically affects the Android platform.
    Affected if Running Google Chrome or Edge Chromium on Android with a vulnerable version

A user is affected if they are running Google Chrome on Android below version 88.0.4324.96 or Microsoft Edge Chromium on Android below version 88.0.705.50, and the Speech Recognizer feature is accessible or utilized.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 88.0.705.50 / 88.0.4324.96 or later
Fixed in 88.0.705.5088.0.4324.96
Interim mitigation

Update Google Chrome on Android to version 88.0.4324.96 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 88.0.4324.96 or later; Edge Chromium 88.0.705.50 or later

  1. 1. Open Google Chrome on your Android device
  2. 2. Navigate to the menu (three dots) > Settings
  3. 3. Tap on 'About Chrome' or 'Chrome'
  4. 4. The browser will automatically check for updates
  5. 5. If an update is available, tap 'Update' to download and install version 88.0.4324.96 or later
  6. 6. Restart the browser after the update completes
  7. For Edge Chromium users: Open Microsoft Edge > Menu > Settings > About Microsoft Edge and update to version 88.0.705.50 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-21124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data