# CVE-2025-9964: Weak Authentication for Root User


- **Severity:** High 8.6 (`CVSS:4.0/AV:P/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
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-7f7w-xxrm-q8hm

## What is CVE-2025-9964?

CVE-2025-9964 is a high-severity vulnerability in Novakon P series (P07, P10, P12, P15), published on 23 Sep 2025. 

### Official description

No password for the root user is set in Novakon P series. This allows phyiscal attackers to enter the console easily. 
This issue affects P series: P – V2001.A.C518o2 until P-2.0.05 Build
                      2026.02.06 (commit d0f97fd9).

Weakness: CWE-521 (Weak Password Requirements)

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


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

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

## Is CVE-2025-9964 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9964 is a high-severity vulnerability in Novakon P series (P07, P10, P12, P15), published on 23 Sep 2025. 
Exploitation: There is no known exploitation of CVE-2025-9964 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-9964/ (Markdown: https://insights.sbomify.com/CVE-2025-9964/index.md)
```

## Sources

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

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