dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-9966

HIGH · 7.3 CVSS v4.0 Published 2025-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 · unedited
Improper privilege management vulnerability in Novakon P series allows attackers to gain root privileges if one service is compromized.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 · moderate confidence

Improper privilege management in Novakon P series devices allows a local attacker who has compromised a single service to escalate privileges to root. This indicates the service runs with excessive privileges or improper separation, enabling privilege escalation beyond the intended security boundaries.

MitigationUpgrade Novakon P series firmware to P-2.0.05 Build 2026.02.06 or later (commit d0f97fd9). Until then, minimize attack surface by restricting network access to the device and ensuring untrusted services cannot run on the affected system.

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
Physical
Complexity
High
Privileges
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Novakon P series device and firmware version
    Access the device's web interface or SSH console and look for the firmware version information, typically found in System Info, Status, or About pages
    Affected if The device is a Novakon P series model running firmware version earlier than P-2.0.05 Build 2026.02.06
  2. Check firmware build date
    Locate the firmware build date in the device's system information panel or via command line if available (e.g., 'show version' or similar)
    Affected if The build date is earlier than 2026.02.06 (or the version cannot be determined to be P-2.0.05 or later)
  3. Verify service privilege configuration
    If you have shell access, examine running processes or services to identify any running with root or elevated privileges (e.g., via 'ps aux' or similar command)
    Affected if Any user-accessible service is running as root or with uid 0, indicating excessive privileges
  4. Compare against affected version range
    Document the exact firmware version string (e.g., P-x.x.x Build YYYY.MM.DD) and compare manually to the fixed release P-2.0.05 Build 2026.02.06
    Affected if The installed version is P-2.0.04 or earlier, or the version cannot be confirmed as P-2.0.05 Build 2026.02.06 or later

You are affected if the Novakon P series device is running firmware earlier than P-2.0.05 Build 2026.02.06, as earlier versions contain the improper privilege management flaw allowing local privilege escalation from a compromised service to root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Novakon P series firmware to P-2.0.05 Build 2026.02.06 or later (commit d0f97fd9). Until then, minimize attack surface by restricting network access to the device and ensuring untrusted services cannot run on the affected system.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9966 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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