ChromeWeb browser · Google
CVE-2026-13976
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 · uneditedInsufficient data validation in Storage in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceInsufficient data validation in Chrome's Storage component prior to version 150.0.7871.47 allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a crafted HTML page. The vulnerability stems from missing input validation in storage-related APIs.
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
< 150.0.7871.47CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify Google Chrome is installedCheck for Chrome executable or check version via command line: 'google-chrome --version' on Linux, 'chrome --version' or check Help > About Google Chrome in the browser on Windows/macOSAffected if Google Chrome is not installed - the system is not affected by this specific Chrome vulnerability
-
Determine installed Chrome versionRun 'google-chrome --version' in terminal, or open Chrome and navigate to chrome://settings/help to view the version numberAffected if Unable to determine the installed version - cannot assess vulnerability status
-
Compare version against affected rangeCompare the installed version number to the affected range: any version prior to 150.0.7871.47 (e.g., 149.x.x.x, 148.x.x.x, etc.) is vulnerableAffected if Installed version is less than 150.0.7871.47 - the browser is in the affected version range and could be vulnerable if an attacker can compromise the renderer process
A user is affected if Google Chrome is installed and the detected version is earlier than 150.0.7871.47, as this vulnerability resides in the Storage component that is always present in Chrome.
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 · scoped150.0.7871.47
Update Google Chrome to version 150.0.7871.47 or later. In enterprise environments, validate browser compatibility with critical web applications before staging the update across the fleet.
Chrome 150.0.7871.47 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 150.0.7871.47, click 'Update Google Chrome' to get the latest version
- Alternatively, download the latest Chrome from google.com/chrome and install it
- Restart Chrome after the update completes
- Verify the version is now 150.0.7871.47 or higher via chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13976 — 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-2026-13976 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