Description

A security vulnerability has been detected in NocteDefensor LudusMCP up to 1.0.24. The impacted element is an unknown function of the file src/tools/ludusEnvironmentGuidesSearch.ts of the component ludus_environment_guides_search. Such manipulation of the argument guide_name leads to path traversal. Local access is required to approach this attack. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.3",
  "pubDate": "2026-08-06T16:16:41.340Z",
  "pubdate": "2026-08-06T16:16:41.340Z",
  "executiveSummary": "A path traversal vulnerability has been identified in NocteDefensor LudusMCP up to version 1.0.24, specifically within the ludus_environment_guides_search component inside the file src/tools/ludusEnvironmentGuidesSearch.ts. This security flaw arises from the improper neutralization of user-supplied input passed to the guide_name argument within an unknown function. Consequently, an attacker capable of manipulating this parameter can traverse the directory structure and access arbitrary files outside the intended operational scope on the underlying filesystem.\nThe risk implication of this vulnerability involves unauthorized disclosure of sensitive local files, configuration data, or system resources accessible to the process context. Exploitation of this security issue requires local access to the target system to approach the attack vector. Although the project maintainers were notified early through an issue report, no official vendor response or corrective patch has been provided as of yet.",
  "technicalDetails": "The vulnerability resides in the src/tools/ludusEnvironmentGuidesSearch.ts file of the ludus_environment_guides_search component in NocteDefensor LudusMCP versions up to 1.0.24. The root cause of the vulnerability is the lack of proper input validation and sanitization on the guide_name argument before it is utilized in file system operations. When an application accepts file identifiers or names from untrusted input without enforcing strict allowlisting or canonical path resolution (such as using path normalization functions to verify the destination remains within the designated base directory), it becomes susceptible to directory traversal techniques.\nThe attack flow proceeds as follows: an adversary with local access to the system interacts with the vulnerable functionality exposed by LudusMCP. The attacker crafts a malicious input string for the guide_name argument containing dot-dot-slash sequences (e.g., ../../../etc/passwd or equivalent relative path notations). Because the vulnerable function processes this input directly or concatenates it insecurely with the base directory path, the file system API traverses upward in the directory hierarchy, bypassing the intended containment boundary.\nRegarding constraints and privileges, the exploitation requires local access to the host executing the application. The network exposure is restricted since local access is a prerequisite to approach the attack surface. The payload behavior involves executing read operations against unauthorized file paths on the host system. The post-exploitation impact includes the potential retrieval of sensitive configuration files, internal application data, or system files depending on the file system permissions granted to the execution context of the LudusMCP process. Because the vendor has not yet responded or released a patch, systems running vulnerable versions remain exposed to unauthorized local file access risks."
}