CVE-2026-19367 Overview
CVE-2026-19367 is a Server-Side Request Forgery (SSRF) vulnerability in NocteDefensor LudusMCP version 1.0.24. The flaw resides in the read_range_config component, specifically within the src/tools/rangeConfig.ts file. Attackers can manipulate the Source argument to coerce the server into issuing unintended outbound HTTP requests. The vulnerability is remotely exploitable and requires low privileges. The project maintainer was notified through an issue report but has not responded at the time of disclosure. This flaw is classified under CWE-918: Server-Side Request Forgery.
Critical Impact
Remote attackers with low-level privileges can abuse the Source parameter in read_range_config to make the LudusMCP server send arbitrary HTTP requests, potentially reaching internal services or metadata endpoints.
Affected Products
- NocteDefensor LudusMCP 1.0.24
- Component: read_range_config
- File: src/tools/rangeConfig.ts
Discovery Timeline
- 2026-08-09 - CVE-2026-19367 published to NVD
- 2026-08-12 - Last updated in NVD database
Technical Details for CVE-2026-19367
Vulnerability Analysis
The vulnerability exists in the read_range_config functionality of LudusMCP, a tool implemented in TypeScript. When a client invokes this function, the server accepts a Source argument that specifies where the range configuration should be read from. The implementation in src/tools/rangeConfig.ts uses this argument directly to construct outbound requests without validating the destination.
An attacker who can reach the LudusMCP interface can supply a URL pointing to internal-only endpoints. The server then performs the request on the attacker's behalf, returning response data or side effects that the attacker could not otherwise access. Typical SSRF targets include cloud metadata services, internal management APIs, and services bound to loopback interfaces.
The EPSS score is 0.209%, indicating low observed exploitation likelihood in the near term. However, LudusMCP operates within lab and range environments that often host sensitive configuration data.
Root Cause
The root cause is missing validation and allowlisting of the user-supplied Source argument. The application treats the parameter as a trusted URL input and forwards requests to whatever destination the caller specifies. There is no scheme restriction, host allowlist, or DNS rebinding protection in the affected code path.
Attack Vector
The attack vector is network-based and requires low privileges. An authenticated user submits a crafted request to the read_range_config endpoint with a Source value pointing to an internal or restricted URL. The server issues the request from its own network position, returning data or triggering actions the attacker cannot reach directly. Full technical details are available in the VulDB CVE Report and the GitHub Issue Tracker.
Detection Methods for CVE-2026-19367
Indicators of Compromise
- Outbound HTTP requests from the LudusMCP process to internal RFC1918 addresses, loopback interfaces, or cloud metadata endpoints such as 169.254.169.254.
- Unexpected Source parameter values in read_range_config invocations containing non-standard schemes such as file://, gopher://, or dict://.
- Anomalous request patterns from the LudusMCP host to services it does not normally communicate with.
Detection Strategies
- Log all invocations of read_range_config and inspect the Source argument for URLs referencing private address space or non-HTTP schemes.
- Monitor egress traffic from hosts running LudusMCP and flag connections to internal management interfaces.
- Correlate application-layer logs with network flow data to identify SSRF probing behavior.
Monitoring Recommendations
- Enable verbose request logging in LudusMCP and forward logs to a centralized SIEM for correlation.
- Configure network-level allowlists that constrain what destinations the LudusMCP host may reach.
- Alert on repeated failed outbound connections that may indicate SSRF port scanning.
How to Mitigate CVE-2026-19367
Immediate Actions Required
- Restrict network access to the LudusMCP interface so only trusted users can invoke read_range_config.
- Deploy an egress firewall policy that blocks the LudusMCP host from reaching internal management ranges and cloud metadata endpoints.
- Audit recent read_range_config calls for suspicious Source values pointing to internal resources.
Patch Information
No official patch is available at the time of publication. The project maintainer has not responded to the vulnerability report filed in the GitHub Issue Tracker. Monitor the LudusMCP repository for updates and apply fixes as soon as they are released.
Workarounds
- Implement a reverse proxy in front of LudusMCP that inspects and filters the Source parameter, rejecting requests targeting private IP ranges and non-HTTPS schemes.
- Run LudusMCP inside a network namespace or container with strict egress rules that prevent access to sensitive internal endpoints.
- Temporarily disable the read_range_config tool if it is not required for current operations.
# Example iptables egress restriction for the LudusMCP host
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -j DROP
iptables -A OUTPUT -d 172.16.0.0/12 -j DROP
iptables -A OUTPUT -d 192.168.0.0/16 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
