CVE-2025-0411
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 · unedited7-Zip Mark-of-the-Web Bypass Vulnerability. This vulnerability allows remote attackers to bypass the Mark-of-the-Web protection mechanism on affected installations of 7-Zip. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of archived files. When extracting files from a crafted archive that bears the Mark-of-the-Web, 7-Zip does not propagate the Mark-of-the-Web to the extracted files. An attacker can leverage this vulnerability to execute arbitrary code in the context of the current user. Was ZDI-CAN-25456.
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 confidenceThis vulnerability allows 7-Zip to extract files from archives without propagating the Mark-of-the-Web (MOTW) security attribute. The MOTW is a Windows feature that flags files downloaded from the internet, triggering security warnings. By failing to preserve this marker on extracted files, 7-Zip allows potentially malicious executable content to bypass Windows' security prompts, enabling arbitrary code execution.
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 dataall versions< 24.09CVSS 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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check 7-Zip versionOpen Control Panel > Programs and Features, or run '7z' from command line with '7z' (no arguments) to see version, or check C:\Program Files\7-Zip\7z.exe properties for version infoAffected if Version displayed is earlier than 24.09 (for example, 24.08, 24.07, etc.)
-
Check for 7-Zip installation pathInspect C:\Program Files\7-Zip\ or C:\Program Files (x86)\7-Zip\ for 7z.exe existence and right-click the executable to view Properties > Details for version numberAffected if 7-Zip executable exists and version is below 24.09
-
Check NetApp Active IQ Unified Manager installationOpen Control Panel > Programs and Features, or check C:\Program Files\NetApp\ or C:\Program Files (x86)\NetApp\ for Active IQ Unified Manager folder presenceAffected if NetApp Active IQ Unified Manager is installed (all versions are affected per vendor advisory)
-
Manual MOTW verification test (optional)Download a test archive from the internet using Edge or Chrome (which apply MOTW), extract a file using 7-Zip, then right-click the extracted file > Properties and check for Zone.Identifier alternate data stream - the extracted file should show a security warning if MOTW was properly propagatedAffected if The extracted file does NOT show a Zone.Identifier security warning in Properties (meaning MOTW was not inherited)
You are affected if 7-Zip version is below 24.09 OR if NetApp Active IQ Unified Manager is installed, as both scenarios involve the vulnerable MOTW-handling code.
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 · scoped24.09
Update 7-Zip to the latest version once the vendor releases a patch. Until then, exercise caution when opening archive files from untrusted sources and consider disabling or restricting file extraction from unknown archives.
7-Zip 24.09 or later
- Download 7-Zip version 24.09 or later from the official 7-Zip website (https://www.7-zip.org/)
- Uninstall the current version of 7-Zip from the system
- Install the updated 7-Zip version 24.09 or later
- Verify the installed version by opening 7-Zip and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0411 — 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-0411 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