ChromeWeb browser · Google
CVE-2025-11216
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 Storage in Google Chrome on Mac prior to 141.0.7390.54 allowed a remote attacker to perform domain spoofing via a crafted video file. (Chromium security severity: Low)
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 confidenceInappropriate implementation in Chrome's Storage component on Mac allowed a remote attacker to perform domain spoofing via a crafted video file. The vulnerability exists in how Chrome handles storage of video file metadata, potentially allowing an attacker to misrepresent the origin domain of a video file.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm Google Chrome is installedOpen /Applications folder and verify Google Chrome.app exists, or run: ls /Applications | grep -i chromeAffected if Google Chrome is not installed on the system
-
Verify the operating system is macOSRun: sw_vers -productVersion or system_profiler SPSoftwareDataType | grep 'System Version'Affected if The operating system is not macOS (this vulnerability specifically affects Chrome on Mac)
-
Obtain the installed Chrome versionOpen Google Chrome, click the three-dot menu, go to Help > About Google Chrome, or run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if Unable to determine the Chrome version
-
Compare version against affected rangeCompare the installed version number to 141.0.7390.54. The format is major.minor.build.patch (e.g., 141.0.7390.54)Affected if Installed version is less than 141.0.7390.54 (e.g., 140.x.x.x or 141.0.7390.53)
User is affected if running Google Chrome on macOS with version less than 141.0.7390.54
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 on Mac to version 141.0.7390.54 or later. No server-side remediation required as this is a client-side browser vulnerability.
141.0.7390.54
- Open Google Chrome on the affected Mac system
- Navigate to Settings > Help > About Google Chrome (or visit chrome://settings/help)
- Chrome will automatically check for available updates
- If version 141.0.7390.54 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the update
- Verify the update was successful by returning to About Google Chrome and confirming the version is 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
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 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-2025-11216 — 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-11216 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