dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021.
ChromeWeb browser · Google

CVE-2021-38000

MEDIUM · 6.1 CVSS v3.1 Published 2021-11-23
Fix available
A fix is available. Upgrade to 95.0.4638.69 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
Insufficient validation of untrusted input in Intents in Google Chrome on Android prior to 95.0.4638.69 allowed a remote attacker to arbitrarily browser to a malicious URL 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

Insufficient validation of untrusted input in Android Intents in Google Chrome allows a remote attacker to force browser navigation to arbitrary malicious URLs via a crafted HTML page. The vulnerability exists in how Chrome processes incoming Intents on Android devices.

MitigationUpdate Google Chrome on Android to version 95.0.4638.69 or later to patch the Intent validation 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:< 95.0.4638.69
FedoraOperating system
Affected:= 34
Debian LinuxOperating system
Affected:= 10.0= 11.0

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
Low
Integrity
Low
Availability
None

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

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 for Android version
    Open Chrome on the Android device, navigate to chrome://version, or go to Settings > Apps > Google Chrome to view the version number
    Affected if Version is lower than 95.0.4638.69
  2. Verify Chrome browser installation on Fedora 34
    Run 'rpm -q google-chrome-stable' or 'dnf list installed | grep chrome' in terminal
    Affected if Package is installed and version is below 95.0.4638.69-1
  3. Verify Chrome browser installation on Debian 10/11
    Run 'dpkg -l | grep chrome' or 'apt list --installed | grep chrome' in terminal
    Affected if Package is installed and version is below 95.0.4638.69-1
  4. Confirm Android Intent handling is enabled
    Chrome on Android handles Intents by default when opening links from external apps; check if the device runs Chrome and processes Intent URIs from web content
    Affected if Chrome for Android is used to handle web links from other apps or web pages

User is affected if Google Chrome on Android or Chrome packages on Fedora 34/Debian 10/11 are below version 95.0.4638.69 and the browser processes Intent-based URLs.

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 95.0.4638.69 or later
Fixed in 95.0.4638.69
Interim mitigation

Update Google Chrome on Android to version 95.0.4638.69 or later to patch the Intent validation vulnerability.

Recommended fix High confidence

Chrome 95.0.4638.69 or later (or latest stable release)

  1. Update Google Chrome on Android to version 95.0.4638.69 or later
  2. For Fedora systems: Run 'sudo dnf update google-chrome-stable' to install the patched version
  3. For Debian-based systems: Run 'sudo apt update && sudo apt upgrade google-chrome-stable' to install the patched version
  4. Restart the Chrome browser after updating to ensure the fix takes effect

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-38000 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