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

> Attackers can use symbolic links on a USB drive to read and modify all files on the NAS via Samba.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-hg9w-23hg-6pfv

## What is CVE-2025-69431?

CVE-2025-69431 is a medium-severity path traversal vulnerability in n/a, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ZSPACE Q2C NAS contains a vulnerability related to incorrect symbolic link following. Attackers can format a USB drive to ext4, create a symbolic link to its root directory, insert the drive into the NAS device's slot, and then access the USB drive's directory mounted on the NAS using the Samba protocol. This allows them to obtain all files within the NAS system and tamper with those files.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Zspace Q2c Firmware.

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

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

## Is CVE-2025-69431 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69431 is a medium-severity path traversal vulnerability in n/a, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69431 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-69431/ (Markdown: https://insights.sbomify.com/CVE-2025-69431/index.md)
```

## Sources

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

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