ChromeWeb browser · Google
CVE-2021-38009
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 cache in Google Chrome prior to 96.0.4664.45 allowed a remote attacker to leak cross-origin data 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 cache implementation prior to version 96.0.4664.45 allowed a remote attacker to leak cross-origin data through a crafted HTML page. The cache improperly handled cross-origin requests, potentially exposing sensitive information from other domains.
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
< 96.0.4664.45
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on that page.Affected if The version shown is earlier than 96.0.4664.45 (for example, 95.x.x.x or earlier)
-
Check Chrome version via command line (Windows)Open Command Prompt and run: chrome --version or go to the Chrome installation folder and run: chrome.exe --versionAffected if The version output is less than 96.0.4664.45
-
Check Chrome version via command line (macOS)Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The version output is less than 96.0.4664.45
-
Check package version on Fedora 34Run: dnf list installed google-chrome-stable (or check the installed package version via rpm -q google-chrome-stable)Affected if The package version is earlier than 96.0.4664.45-1
-
Check package version on Debian 10/11Run: dpkg -l | grep google-chrome-stable (or apt show google-chrome-stable)Affected if The installed package version is earlier than 96.0.4664.45
You are affected if your installed Google Chrome version (or Linux package version) is earlier than 96.0.4664.45.
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 · scoped96.0.4664.45
Upgrade Google Chrome to version 96.0.4664.45 or later to patch the cache vulnerability.
Chrome 96.0.4664.45 or later
- Update Google Chrome to version 96.0.4664.45 or later by navigating to Chrome menu > Help > About Google Chrome and clicking 'Update'
- For Fedora systems: run 'sudo dnf update' or 'sudo dnf upgrade google-chrome-stable' to install the patched Chrome package
- For Debian systems: run 'sudo apt update && sudo apt upgrade' to apply the patched Chrome package
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38009 — 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-38009 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