# CVE-2025-50328: Security feature bypass in n/a

> B1 Free Archiver fails to propagate Zone.Identifier, allowing extracted files to bypass Windows SmartScreen and execute untrusted code.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-vh8g-ch7v-39pg

## What is CVE-2025-50328?

CVE-2025-50328 is a high-severity vulnerability in n/a, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in B1 Free Archiver v1.5.86 allows files extracted from downloaded archives to bypass Windows Mark of the Web (MotW) protections. When an archive is downloaded from the internet and extracted using B1 Free Archiver, the software fails to propagate the 'Zone.Identifier' alternate data stream to the extracted files. As a result, these files can be executed without triggering Windows Defender SmartScreen warnings or security prompts, enabling untrusted code execution without standard security restrictions.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

No fix has been published for CVE-2025-50328 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50328 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50328 is a high-severity vulnerability in n/a, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50328 exists.

Affected product: n/a. 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-50328/ (Markdown: https://insights.sbomify.com/CVE-2025-50328/index.md)
```

## Sources

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

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