CVE-2025-9965
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper authentication vulnerability in Novakon P series allows unauthenticated attackers to upload and download any application from/to the device.This issue affects P series: P – V2001.A.C518o2 until P-2.0.05 Build 2026.02.06 (commit d0f97fd9).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper authentication in Novakon P series devices allows unauthenticated attackers to bypass authentication and upload/download any application to/from the device. The vulnerability stems from missing or ineffective authentication checks on application upload/download functions, enabling complete device compromise without credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Novakon P series deviceCheck the device model or system information on the target device to confirm it is a Novakon P series device. This may be visible in the device web interface, system status page, or CLI output.Affected if The device is a Novakon P series model and is running firmware prior to P-2.0.05 Build 2026.02.06
-
Determine firmware versionLocate the firmware version information in the device management interface, typically found under System, Status, or About sections. Compare the installed version against P-2.0.05 Build 2026.02.06.Affected if The installed firmware version is earlier than P-2.0.05 Build 2026.02.06
-
Locate application upload/download functionsIdentify whether the device provides application upload or download functionality in its management interface. Look for features labeled as Application, Firmware Upload, Backup, Export, or similar in the web interface or CLI.Affected if The device exposes application upload or download features in its management interface without requiring authentication for these functions
-
Verify authentication enforcement on upload/downloadTest whether the application upload and download endpoints require valid credentials. Attempt to access these functions without providing credentials or from an unauthenticated state.Affected if Application upload and download functions are accessible without authentication or accept requests without proper credential validation
A user is affected if they operate a Novakon P series device with firmware earlier than P-2.0.05 Build 2026.02.06 that exposes unauthenticated application upload/download functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Novakon P series firmware to P-2.0.05 Build 2026.02.06 or later. If immediate upgrade is not possible, restrict network access to the device's management interface using firewall rules or network segmentation.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9965 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data