CVE-2026-19047

Deferred Deferred - Pending Action

Command Injection in NocteDefensor LudusMCP

Publication date: 2026-08-06

Last updated on: 2026-08-12

Assigner: VulDB

Description

A vulnerability was detected in NocteDefensor LudusMCP up to 1.0.24. This affects the function executeArbitraryCommand/executeCommand of the file src/ludusMCP/cliWrapper.ts of the component ludus_cli_execute. Performing a manipulation of the argument command/args results in command injection. The attack needs to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-06

Last Modified

2026-08-12

Generated

2026-08-16

AI Q&A

2026-08-06

EPSS Evaluated

2026-08-15

NVD

CVE-2026-19047

EUVD

EUVD-2026-54087

Affected Vendors & Products

Vendor	Product	Version / Range
noctedefensor	ludusmcp	to 1.0.24 (inc)

Helpful Resources

Exploitability

CWE

KEV

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.
CWE-74	The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Attack-Flow Graph

Executive Summary

This is a command injection vulnerability in NocteDefensor LudusMCP up to version 1.0.24. The issue occurs in the executeArbitraryCommand/executeCommand function of src/ludusMCP/cliWrapper.ts. When the primary execution path fails, the system falls back to reconstructing the command as a shell string and passes it to execSync() without proper sanitization. User-controlled command/args parameters can include shell metacharacters, allowing arbitrary command execution during the fallback path.

The primary path uses spawn() with shell: false which is safe, but the fallback execSync() path is vulnerable because it processes untrusted input as a shell string.

Detection Guidance

To detect this vulnerability, check if LudusMCP version 1.0.24 or earlier is installed. Look for the vulnerable functions executeArbitraryCommand or executeCommand in src/ludusMCP/cliWrapper.ts. Monitor for unexpected command execution attempts or shell metacharacters in logs.

Impact Analysis

An attacker with local access could execute arbitrary commands on the system where LudusMCP is running. This could lead to unauthorized file access, data exfiltration, system compromise, or installation of malware. The impact is limited to local attacks since the vulnerability requires local access to exploit.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR (data protection) and HIPAA (health information security) by allowing unauthorized access to sensitive data. Organizations using affected versions may face compliance violations, legal penalties, and reputational damage if exploited.

Mitigation Strategies

Immediately update LudusMCP to the latest version beyond 1.0.24. If an update is unavailable, disable the ludus_cli_execute tool or restrict access to it. Review and sanitize all command and args inputs in the CLI fallback mechanism.

Hi! I’m here to help you understand CVE-2026-19047. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70