# CVE-2025-0411: 7-Zip Mark of the Web Bypass

> Attackers can bypass Mark-of-the-Web protections in 7-Zip to execute arbitrary code by tricking users into opening malicious archives.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 6 Feb 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jan 2025
- **Updated:** 26 Feb 2026
- **Also known as:** CLEANSTART-2025-EQ95920, GHSA-2pjx-wvcg-vhr8

## What is CVE-2025-0411?

CVE-2025-0411 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 25 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

7-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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-0411?

It affects 2 products.


Products: 7-Zip 7-Zip, Netapp Active Iq Unified Manager.

## How do I fix CVE-2025-0411?

Upgrade to a fixed version. US federal agencies must fix it by 27 Feb 2025.

## Is CVE-2025-0411 being exploited?

Yes. Attackers have exploited CVE-2025-0411 in the wild since at least 6 Feb 2025.

Public exploit code:

- This repository contains POC scenarios as part of CVE-2025-0411 MotW bypass. (github_poc): https://github.com/dhmosfunk/7-Zip-CVE-2025-0411-POC
- https://github.com/c4bsec/7-Zip-CVE-2025-0411-POC (github_poc): https://github.com/c4bsec/7-Zip-CVE-2025-0411-POC
- 7-Zip Mark-of-the-Web绕过漏洞PoC(CVE-2025-0411) (github_poc): https://github.com/iSee857/CVE-2025-0411-PoC
- https://github.com/ishwardeepp/CVE-2025-0411-MoTW-PoC (github_poc): https://github.com/ishwardeepp/CVE-2025-0411-MoTW-PoC
- CVE-2025-0411 7-Zip Mark-of-the-Web Bypass (github_poc): https://github.com/betulssahin/CVE-2025-0411-7-Zip-Mark-of-the-Web-Bypass
- Rust Macros No Recoil Guide 🚀 Boost Aim Like a Pro in C and Python (github_poc): https://github.com/RustMacrosRecoil/7-Zip-CVE-2025-0411-POC

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2008-6536](https://insights.sbomify.com/CVE-2008-6536/): Other in n/a (critical 10.0)
- [CVE-2026-48095](https://insights.sbomify.com/CVE-2026-48095/): GHSL-2026-140_7-Zip: 7-Zip has a heap buffer overflow via NTFS compressed stream buffer under-allocation (high 8.8)
- [CVE-2018-10172](https://insights.sbomify.com/CVE-2018-10172/): Privilege escalation in n/a (high 8.8)
- [CVE-2016-2335](https://insights.sbomify.com/CVE-2016-2335/): Memory corruption in n/a (high 8.8)
- [CVE-2024-11477](https://insights.sbomify.com/CVE-2024-11477/): 7-Zip Zstandard Decompression Integer Underflow Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0411 and fix it if it is affected.

What it is: CVE-2025-0411 is a high-severity vulnerability in Netapp Active Iq Unified Manager, published on 25 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-0411 in the wild since at least 6 Feb 2025.

Affected product: Netapp Active Iq Unified Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0411/ (Markdown: https://insights.sbomify.com/CVE-2025-0411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0411
- OSV: https://osv.dev/vulnerability/CVE-2025-0411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0411/
Summaries are generated and may contain mistakes; the official description above is the record.