ChromeWeb browser · Google
CVE-2021-38003
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 · uneditedInappropriate implementation in V8 in Google Chrome prior to 95.0.4638.69 allowed a remote attacker to potentially exploit heap corruption 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 confidenceA vulnerability in Google Chrome's V8 JavaScript engine (versions prior to 95.0.4638.69) allows remote attackers to exploit heap corruption via malicious HTML pages. The issue stems from an inappropriate implementation in V8 that can be triggered when a user visits a specially crafted webpage.
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
< 95.0.4638.69
FedoraOperating system
= 34
Debian LinuxOperating system
= 10.0= 11.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is lower than 95.0.4638.69
-
Confirm V8 JavaScript engine is enabledNavigate to chrome://settings/content/javascript in Chrome settingsAffected if JavaScript is allowed (this is the default and required setting for the exploit to work)
-
Check Chromium-based browser variantRun 'google-chrome --product-version' or check package manager for installed chromium package on Fedora/DebianAffected if Using Google Chrome or a Chromium package on Fedora 34 or Debian 10/11 with version below 95.0.4638.69
You are affected if you are running Google Chrome or a Chromium-based browser on the listed platforms with a version lower than 95.0.4638.69 and JavaScript execution is enabled (which is the default state).
Generated from the published advisory. Verify against your own configuration.
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 · scoped95.0.4638.69
Update Google Chrome to version 95.0.4638.69 or later to patch the V8 engine vulnerability. Organizations should deploy browser updates via their patch management infrastructure and verify compliance.
Chrome 95.0.4638.69 or later (or latest stable channel)
- For system-installed Chrome/Chromium (Fedora): Run `sudo dnf update` to apply security updates including the Chrome fix
- For system-installed Chromium (Debian): Run `sudo apt-get update && sudo apt-get upgrade` to apply security updates
- For direct Chrome installation: Download and install Chrome 95.0.4638.69 or later from https://www.google.com/chrome/
- Verify the installed version by navigating to chrome://settings/help in the browser
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38003 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-38003 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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