# CVE-2025-69601: Path traversal in n/a

> Attackers can exploit Zip Slip in 66biolinks to write files outside intended directories, enabling content defacement or overwriting sensitive files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-3mpf-56v2-rjgc

## What is CVE-2025-69601?

CVE-2025-69601 is a medium-severity path traversal vulnerability in n/a, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A directory traversal (Zip Slip) vulnerability exists in the “Static Sites” feature of 66biolinks v44.0.0 by AltumCode. Uploaded ZIP archives are automatically extracted without validating or sanitizing file paths. An attacker can include traversal sequences (e.g., ../) in ZIP entries to write files outside the intended extraction directory. This allows static files (html, js, css, images) file write to unintended locations, or overwriting existing HTML files, potentially leading to content defacement and, in certain deployments, further impact if sensitive files are overwritten.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Altumcode 66biolinks.

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

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

## Is CVE-2025-69601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-69602](https://insights.sbomify.com/CVE-2025-69602/): Auth bypass in n/a (critical 9.1)
- [CVE-2025-66939](https://insights.sbomify.com/CVE-2025-66939/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69601 is a medium-severity path traversal vulnerability in n/a, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69601 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-69601/ (Markdown: https://insights.sbomify.com/CVE-2025-69601/index.md)
```

## Sources

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

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