ChromeWeb browser · Google
CVE-2026-11199
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 WebRTC in Google Chrome prior to 149.0.7827.53 allowed an attacker in a privileged network position to leak cross-origin data via malicious network traffic. (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 confidenceWebRTC in Google Chrome had an implementation flaw that allowed an attacker with privileged network position (e.g., MITM) to intercept or manipulate WebRTC network traffic (likely ICE candidates or related signaling) to leak cross-origin data. The vulnerability exists in versions prior to 149.0.7827.53.
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
< 149.0.7827.53CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 versionNavigate to chrome://settings/help or enter chrome://version in the address bar to view the installed Chrome versionAffected if Version is lower than 149.0.7827.53
-
Verify WebRTC is accessibleVisit a WebRTC test site (such as webrtc.github.io) or check browser policies for WebRTC availability. In enterprise environments, review Chrome policies under chrome://policy for WebRTC-related settingsAffected if WebRTC is enabled or accessible in the browser and Chrome version is below 149.0.7827.53
-
Review WebRTC policies (enterprise)Check Chrome policy settings for WebRTC restrictions by examining registry keys (Windows: HKLM\SOFTWARE\Policies\Google\Chrome, macOS: /Library/Preferences/com.google.Chrome.plist, Linux: /etc/chromium/policies) or using chrome://policyAffected if No restrictive WebRTC policies are enforced and Chrome version is below 149.0.7827.53
You are affected if your installed Google Chrome version is below 149.0.7827.53 and WebRTC is accessible or enabled in your environment.
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 · scoped149.0.7827.53
Update Google Chrome to version 149.0.7827.53 or later. Since this is a client-side browser vulnerability, the fix is simply patching the Chrome installation.
Chrome 149.0.7827.53 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- If the version is below 149.0.7827.53, update Chrome by clicking 'Update Google Chrome' (or Chrome will update automatically on restart)
- Restart Chrome to apply the update
- Verify the version is now 149.0.7827.53 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
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11199 — 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-11199 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