dbcve.org
ChromeWeb browser · Google

CVE-2026-11208

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Use after free in Codecs in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to obtain potentially sensitive information from process memory 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 confidence

This is a use-after-free vulnerability in the Codecs component of Google Chrome that allows a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. The vulnerability exists in versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to remediate this vulnerability.

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
Affected:< 149.0.7827.53

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help in Chrome or use 'About Google Chrome' from the Help menu to view the version number
    Affected if The displayed version is lower than 149.0.7827.53 (for example, 149.0.7827.0 or any earlier version)
  2. Verify Chrome is configured to use Codecs for media playback
    Ensure Chrome can play media files - the vulnerability triggers when Chrome processes a crafted HTML page containing media that uses the Codecs component. Test by loading any HTML page with embedded video or audio.
    Affected if Chrome successfully renders media content, meaning the Codecs component is active and the attack surface exists
  3. Confirm Chrome is not running in a restricted mode
    Check if Chrome is running with enterprise policies that disable media codecs, or in a sandboxed/kiosk mode that limits codec functionality. Review any applied Chrome policies via chrome://policy.
    Affected if Chrome allows media playback without policy restrictions, indicating the Codecs component is fully operational and vulnerable to the use-after-free condition
  4. Identify if the Chrome channel is an affected branch
    Check whether Chrome is installed via Stable, Beta, Dev, or Canary channel. Run 'chrome://version' to see the installation path and channel information.
    Affected if Chrome is on the Stable, Beta, or Dev channel at a version prior to 149.0.7827.53 - these branches receive the vulnerable codec code before the fix

A user is affected if their installed Chrome version is below 149.0.7827.53 and the browser can process media content using the Codecs component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click on 'About Google Chrome'
  5. The browser will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome'
  7. Restart the browser to apply the update
  8. Alternatively, download the latest Chrome installer from the official Google Chrome website (google.com/chrome) and run it to update
Caveat Chrome updates typically have minimal breaking changes; minor browser behavior or extension compatibility differences may occur

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
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11208 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11208 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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