dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-22103

CRITICAL · 9.3 CVSS v4.0 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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
The NPC start endpoint on the web server at port 8090 is vulnerable to command injection.

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

The NPC start endpoint on the web server at port 8090 does not properly sanitize user input before passing it to system commands, allowing an attacker to inject arbitrary OS commands. This remote, unauthenticated command injection can lead to complete system compromise.

MitigationImplement strict input validation and use parameterized APIs or safe command-execution methods instead of shell command concatenation. Restrict network access to port 8090 and apply authentication to the endpoint.

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:H/VI:H/VA:H/SC:N/SI:N/SA:N/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. Verify port 8090 is open and listening
    Run 'netstat -tuln | grep 8090' or 'ss -tuln | grep 8090' to confirm the service is exposed on port 8090
    Affected if Port 8090 is open and accepting connections indicates potential exposure to this vulnerability
  2. Identify the service on port 8090
    Use 'curl -v http://localhost:8090/' or 'nmap -sV -p 8090 <target>' to probe the service and identify the product name and version banner
    Affected if The service is identified as the affected NPC server product with a version matching the vulnerable range
  3. Confirm NPC start endpoint exists
    Send a request to the NPC start endpoint using 'curl -X POST http://<target>:8090/npc/start' or similar path that triggers the vulnerable command execution
    Affected if The endpoint responds (even with an error) confirming the NPC start functionality is present
  4. Test for unauthenticated access
    Attempt to access the NPC start endpoint without providing any credentials or authentication tokens
    Affected if The endpoint accepts requests without requiring authentication, indicating the flaw is exploitable
  5. Check for input sanitization weakness
    Send a test payload with special characters (e.g., ';whoami' or '|id') to the NPC start endpoint and observe if the input is passed to system commands
    Affected if The response reflects injected characters or executes system commands, confirming the injection vulnerability exists

The system is affected if port 8090 is open, an NPC start endpoint exists that accepts unauthenticated requests, and user input is passed unsanitized to system commands.

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

Implement strict input validation and use parameterized APIs or safe command-execution methods instead of shell command concatenation. Restrict network access to port 8090 and apply authentication to the endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22103 — 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-2026-22103 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