# CVE-2025-9963: Path Traversal

> Attackers can exploit path traversal to access the root file system and modify files with root permissions, compromising the device.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 23 Sep 2025
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-4whh-r2w5-9vf6

## What is CVE-2025-9963?

CVE-2025-9963 is a critical path traversal vulnerability in Novakon P series (P07, P10, P12, P15), published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A path traversal vulnerability in Novakon P series allows to expose the root file system "/" and modify all files with root permissions. This way the system can also be compromized.This issue affects P series: P – V2001.A.C518o2 until P-2.0.05 Build
                      2026.02.06 (commit d0f97fd9).

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

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


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

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

## Is CVE-2025-9963 being exploited?

There is no known exploitation of CVE-2025-9963 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9963 is a critical path traversal vulnerability in Novakon P series (P07, P10, P12, P15), published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9963 in the wild and no public exploit code.

Affected product: Novakon P series (P07, P10, P12, P15). 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-9963/ (Markdown: https://insights.sbomify.com/CVE-2025-9963/index.md)
```

## Sources

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

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