ChromeWeb browser · Google
CVE-2025-12905
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 Downloads in Google Chrome on Windows prior to 140.0.7339.80 allowed a remote attacker to bypass Mark of the Web via a crafted HTML page. (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 confidenceGoogle Chrome's Downloads component on Windows had an implementation flaw that allowed crafted HTML pages to bypass Mark of the Web (MOTW) protections. MOTW is a Windows security feature that adds Zone.Identifier metadata to downloaded files to warn users about potentially unsafe content from the internet. This bypass could cause users to open downloaded HTML files without the expected security warnings.
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
< 140.0.7339.80CVSS 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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/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.
-
Verify Chrome is installed on WindowsCheck for Google Chrome in the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or look for chrome.exe in Program Files or Program Files (x86)Affected if Google Chrome browser is present on the Windows system
-
Determine installed Chrome versionOpen Chrome, go to Menu > Help > About Google Chrome, or run 'chrome --version' from Command Prompt, or check the Version value in the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google ChromeAffected if Cannot retrieve a version number (Chrome may be installed but version tracking is disabled)
-
Compare version against affected rangeCompare the installed version number to 140.0.7339.80 - any version below this (e.g., 140.0.7339.79, 139.x.x.x, 138.x.x.x) falls within the vulnerable rangeAffected if Installed version is less than 140.0.7339.80 (for example, 139.0.7376.15 or 138.0.5351.112)
If Google Chrome version on Windows is below 140.0.7339.80, the Downloads component may allow HTML files to bypass Mark of the Web security warnings.
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 · scoped140.0.7339.80
Update Google Chrome to version 140.0.7339.80 or later on all Windows workstations. No additional configuration or enterprise policy changes are required.
Chrome 140.0.7339.80 or later for Windows
- Open Google Chrome on Windows
- Click the three-dot menu in the top-right corner
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates and automatically download version 140.0.7339.80 or later
- Click 'Restart' to apply the update
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
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12905 — 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-12905 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