ChromeWeb browser · Google
CVE-2026-14015
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 · uneditedRace in WebRTC in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker to leak cross-origin data 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 · moderate confidenceA race condition in WebRTC in Google Chrome on Windows before version 150.0.7871.47 allows a remote attacker to leak cross-origin data via a crafted HTML page. The vulnerability stems from improper synchronization in the WebRTC implementation that can be exploited by winning a race condition between WebRTC operations.
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
- 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.
-
Check Chrome version on WindowsOpen Chrome and navigate to chrome://settings/help, or run 'chrome --version' from command line, or check 'About Google Chrome' in the Chrome menuAffected if Installed version is lower than 150.0.7871.47 (e.g., 149.x.x.x or earlier)
-
Confirm Windows platformThis vulnerability specifically affects Chrome on Windows; check your operating system is WindowsAffected if Running Chrome on Windows (the vulnerability does not apply to macOS or Linux according to the advisory)
-
Verify WebRTC is enabledWebRTC is enabled by default in Chrome; to confirm, go to chrome://settings/content and check 'WebRTC' settings, or visit a WebRTC leak test siteAffected if WebRTC is enabled (default state) - the vulnerability requires WebRTC to be active to exploit the race condition
You are affected if you are running Google Chrome on Windows with a version lower than 150.0.7871.47 and WebRTC is enabled (default).
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 the vulnerability. Users should ensure their browser auto-updates or manually check for updates via chrome://settings/help.
Chrome 150.0.7871.47 or later
- 1. Verify the current Google Chrome version by navigating to chrome://settings/help or checking About Chrome in the menu.
- 2. If the installed version is prior to 150.0.7871.47, initiate an update by clicking 'Update Google Chrome' in the settings page.
- 3. Restart the browser to complete the update process.
- 4. Confirm the version has been updated to 150.0.7871.47 or later after restart.
- 5. For enterprise deployments, use group policy or management tools to push the update to affected Windows machines.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14015 — 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-14015 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