CVE-2026-22103
Deferred Deferred - Pending Action

Command Injection in Web Server Port 8090

Vulnerability report for CVE-2026-22103, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Dutch Institute for Vulnerability Disclosure

Description

The NPC start endpoint on the web server at port 8090 is vulnerable to command injection.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-77 The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the NPC start endpoint on the web server running on port 8090. It is susceptible to command injection, meaning an attacker can execute arbitrary commands on the server by exploiting this endpoint.

Detection Guidance

To detect the vulnerability described in CVE-2026-22103, you can check if the NPC start endpoint on port 8090 of a web server is exposed and vulnerable to command injection. Below are some suggested steps and commands to help identify the issue.

  • Identify if port 8090 is open and accessible on the target system. You can use network scanning tools like nmap to check for open ports.
  • Example nmap command: nmap -p 8090 <target_IP_or_hostname>
  • If the port is open, manually inspect the NPC start endpoint for signs of command injection. This can be done by sending crafted HTTP requests to the endpoint and observing the responses for unusual behavior or command execution.
  • Example curl command to test for command injection: curl "http://<target_IP_or_hostname>:8090/npc/start?param=test;id"
  • Monitor the response for signs of command execution, such as output from the 'id' command or other unexpected behavior.
  • Use vulnerability scanning tools that support detection of command injection flaws, such as OWASP ZAP or Burp Suite, to automate the testing process.
Impact Analysis

Because the vulnerability allows command injection without any privileges or user interaction, an attacker can remotely execute arbitrary commands on the affected server. This can lead to full compromise of the system, data theft, service disruption, or further attacks within the network.

Compliance Impact

This vulnerability, involving command injection on a web server endpoint, can have significant implications for compliance with standards and regulations like GDPR and HIPAA.

  • GDPR: The vulnerability could lead to unauthorized access or exfiltration of personal data, violating GDPR's requirements for data protection and confidentiality (Articles 5, 25, and 32). A successful exploit may result in a data breach, triggering mandatory reporting obligations under Article 33 and potential fines under Article 83.
  • HIPAA: If the affected system processes or stores protected health information (PHI), this vulnerability could lead to unauthorized access or disclosure of PHI, violating the HIPAA Security Rule (45 CFR Part 164, Subpart C). This may result in non-compliance penalties and required corrective actions.
  • Other standards: The vulnerability's high CVSS score (9.3) indicates severe risk, which may violate requirements in standards like ISO 27001 (controls A.12.2.1, A.12.6.1) or NIST SP 800-53 (controls SI-10, SI-15), which mandate protection against injection attacks and secure system configurations.

Organizations must address this vulnerability promptly to avoid compliance violations, potential legal consequences, and reputational damage.

Mitigation Strategies

To mitigate the command injection vulnerability in the NPC start endpoint on port 8090, follow these immediate steps.

  • Restrict access to the vulnerable endpoint by implementing network-level controls, such as firewalls or access control lists (ACLs), to block external access to port 8090.
  • Disable the NPC start endpoint if it is not required for normal operations. Consult the vendor or system documentation for instructions on disabling specific endpoints.
  • Apply input validation and sanitization to the NPC start endpoint to prevent command injection attacks. Ensure that user-supplied input is strictly validated and sanitized before processing.
  • Update the web server software or application to the latest version, if a patch or update is available from the vendor. Monitor the vendor's security advisories for updates related to this vulnerability.
  • Implement a web application firewall (WAF) to filter and block malicious requests targeting the vulnerable endpoint.
  • Monitor logs for suspicious activity related to the NPC start endpoint, such as unusual command execution attempts or unexpected input patterns.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-22103. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart