ChromeWeb browser · Google
CVE-2026-13900
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 Chromecast in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions 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 confidenceThis is a navigation restriction bypass vulnerability in Chrome's Chromecast functionality. A remote attacker who has already compromised the renderer process can exploit an inappropriate implementation to bypass navigation restrictions via a crafted HTML page. The vulnerability exists in Chrome versions prior to 150.0.7871.47.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Google Chrome versionNavigate to chrome://settings/help in the Chrome browser, or click Menu > Help > About Google Chrome. The version number is displayed on that page.Affected if The displayed version is lower than 150.0.7871.47
-
Check Chrome version via command line (optional)On Windows, run 'chrome --version' from Command Prompt or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' properties. On macOS, run 'grep -a "CFBundleShortVersionString" /Applications/Google\ Chrome.app/Contents/Info.plist' in Terminal.Affected if The reported version is lower than 150.0.7871.47
-
Verify if Chromecast functionality is enabledIn Chrome, go to Settings > Privacy and Security > Site Settings > Additional content settings, or type 'chrome://settings/content' in the address bar. Look for Cast, Media Router, or Chromecast-related settings.Affected if Chromecast or Cast media routing is enabled and the Chrome version is below 150.0.7871.47
You are affected if Google Chrome version is below 150.0.7871.47 and the Chromecast/Cast feature is enabled in the browser.
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 to patch this vulnerability. Organizations using Chromecast functionality should verify the update is applied across all managed endpoints.
Chrome 150.0.7871.47 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is below 150.0.7871.47, Chrome will automatically check for and download updates
- Alternatively, download the latest Google Chrome from the official website (google.com/chrome)
- Restart Chrome after the update completes to apply the fix
- Verify the version now shows 150.0.7871.47 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13900 — 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-13900 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