dbcve.org
ChromeWeb browser · Google

CVE-2026-11041

HIGH · 8.8 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Insufficient validation of untrusted input in Media in Google Chrome on Windows prior to 149.0.7827.53 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 · moderate confidence

Insufficient validation of untrusted input in Chrome's Media component on Windows prior to version 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later on Windows systems 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Google Chrome version on Windows
    Open Chrome, click the three-dot menu, select 'Help', then 'About Google Chrome'. Alternatively, navigate to chrome://settings/help in the address bar. Note the version number displayed.
    Affected if The displayed version is lower than 149.0.7827.53 (for example, 149.0.7827.52 or earlier)
  2. Verify Windows platform
    Confirm the Chrome installation is running on Windows. This vulnerability only affects Chrome on Windows, not macOS or Linux.
    Affected if Chrome is running on any Windows version and the version from step 1 is below 149.0.7827.53
  3. Confirm Media component usage
    The vulnerability exists in Chrome's Media component (used for audio/video playback). This component is built into Chrome and does not require any special configuration to be present.
    Affected if Chrome is used for any media playback (video/audio) on Windows and version is below 149.0.7827.53
  4. Check for renderer process compromise indicators
    Review any endpoint detection logs or browser security events for signs of renderer process compromise. The vulnerability requires an already compromised renderer process to be exploitable.
    Affected if Evidence exists of renderer process compromise AND Chrome version is below 149.0.7827.53 on Windows

A Windows user is affected if their Google Chrome version is below 149.0.7827.53 and they are running on Windows, regardless of Media component usage since the component is built-in and enabled by default.

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 on Windows systems to remediate this vulnerability.

Recommended fix High confidence

Chrome 149.0.7827.53 or later (stable release)

  1. Open Google Chrome on your Windows machine
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for and download any available updates
  6. Once the update to version 149.0.7827.53 or later is downloaded, click 'Relaunch' to restart the browser and apply the update
  7. Verify the update was successful by returning to Help > About Google Chrome and confirming the version is 149.0.7827.53 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11041 — 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-11041 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