Skip to main content
VulnerabilityPublished Updated

CVE-2026-19366: NocteDefensor LudusMCP · Path Traversal

Affects NocteDefensor LudusMCPSource CVE Database V5

0
Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
NocteDefensorLudusMCPAffected
  • 1.0.0 – 1.0.24
25 affected builds
Fixed in–
GitHubnoctedefensor/LudusMCPpkg:github/noctedefensor/LudusMCPOther threatsAffected
  • 1.0.0 – 1.0.24
25 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:noctedefensor:ludusmcp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vendor has not responded or released a fix, users should restrict local access to trusted users only and monitor for any updates from the vendor regarding patches or mitigations.

Description

A flaw has been found in NocteDefensor LudusMCP up to 1.0.24. Affected is an unknown function of the file src/tools/insertCredsRangeConfig.ts of the component insert_creds_range_config. Executing a manipulation of the argument configPath/outputPath can lead to path traversal. The attack is restricted to local execution. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…