Skip to main content

CVE-2025-04117-Zip Mark of the Web Bypass Vulnerability

Patch nowHigh7.0Exploited, CISA due date 2025-02-27EPSS 48%, higher than 99% of scored CVEs

CVE-2025-0411 is a protection mechanism failure in 7-Zip, rated high (7.0 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

A security control can be bypassed or does not work as intended.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker use a weak default the deployment never changed.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2025-02-06: it is being exploited in the wild. EPSS estimates a 48% chance of exploitation activity in the next 30 days, higher than 99% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2025-02-27.
  2. Upgrade 7-Zip to 24.09 or later.
  3. Limit who can run code or sign in on the hosts that run it.
  4. Warn the people who use it, and filter files and links on the way in.
  5. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Default settings, permissions and deployment configuration. The flaw sits between the shipped defaults and a hardened deployment.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Between the shipped defaults and a hardened deployment. An attacker who crosses it can use a weak default the deployment never changed.

Questions to answer about your own systems

  • Where does 7-Zip run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.