ChromeWeb browser · Google
CVE-2025-11211
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 · uneditedOut of bounds read in Media in Google Chrome prior to 141.0.7390.54 allowed a remote attacker to potentially perform out of bounds memory access 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 confidenceAn out of bounds read vulnerability exists in the Media component of Google Chrome versions prior to 141.0.7390.54. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially allowing unauthorized memory access.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/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.
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.Affected if The version shown is less than 141.0.7390.54 (for example, 141.0.7390.53 or any earlier version).
-
Verify exact version stringOn chrome://version, locate the 'Version' field. Compare the full version number including the build suffix (the number after the dot, e.g., 7390.53).Affected if The full version string begins with a number lower than 141.0.7390.54 when compared numerically.
-
Confirm Chrome is the browser in useVerify that the browser accessing potentially malicious HTML content is Google Chrome and not a Chromium-based alternative (such as Edge, Brave, or Opera) which may have different version numbers.Affected if The browser is Google Chrome specifically, and its version is below 141.0.7390.54.
A user is affected if they are running Google Chrome with any version number lower than 141.0.7390.54, since the vulnerability exists in the Media component of all prior 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
Update Google Chrome to version 141.0.7390.54 or later to patch this vulnerability.
Chrome 141.0.7390.54 or later
- Open Google Chrome and navigate to Settings > About Chrome to check the current version
- If the version is below 141.0.7390.54, click 'Update Google Chrome' to install the latest version
- Restart the browser to complete the update
- Verify the update was successful by checking Settings > About Chrome shows version 141.0.7390.54 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11211 — 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-11211 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