ChromeWeb browser · Google
CVE-2025-11206
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 · uneditedHeap buffer overflow in Video in Google Chrome prior to 141.0.7390.54 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
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 confidenceHeap buffer overflow vulnerability in Google Chrome's video processing component allows a remote attacker to potentially escape the sandbox and execute arbitrary code by tricking users into visiting a crafted HTML page containing malicious video content.
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
< 141.0.7390.54CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify installed Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome in the Chrome menu to display the current version numberAffected if Version number is less than 141.0.7390.54
-
Check Chrome version via command lineOn Windows, run 'chrome --version' in command prompt; on macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal; on Linux, run 'google-chrome --version' or 'chromium --version'Affected if Reported version is below 141.0.7390.54
-
Verify video processing component presenceThe vulnerable component (video processing) is built into Chrome and requires no special configuration - all Chrome installations with affected versions contain this componentAffected if Chrome version is in the affected range, meaning the video processing component contains the heap buffer overflow vulnerability
You are affected if Google Chrome is installed with a version lower than 141.0.7390.54, as the heap buffer overflow exists in the built-in video processing component of those versions.
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 · scoped141.0.7390.54
Upgrade Google Chrome to version 141.0.7390.54 or later. In enterprise environments, deploy the update via centralized patch management and verify completion across all affected endpoints.
Chrome 141.0.7390.54 or later
- 1. Verify current Chrome version by navigating to chrome://settings/help or checking About Google Chrome
- 2. Download Chrome version 141.0.7390.54 or later from the official Chrome release channel (chromereleases.googleblog.com)
- 3. Install the update - Chrome typically auto-updates but manual download ensures the fix
- 4. Restart Chrome to complete the update installation
- 5. Verify the version now shows 141.0.7390.54 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11206 — 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-2025-11206 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