Skip to content
Fencer Intel
critical 9.8

CVE-2026-23744 in the critical feed json

REC in MCPJam inspector due to HTTP Endpoint exposes

published 9mo ago modified 4mo ago also GHSA-232v-j27c-5pp6 , EUVD-2026-2859

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
67.5%
EPSS 67.5% chance of exploitation in 30 days, percentile 99.3%
public exploits
2
Metasploit and Exploit-DB, plus a Nuclei check

Summary

MCPJam inspector is the local-first development platform for MCP servers. Versions 1.4.2 and earlier are vulnerable to remote code execution (RCE) vulnerability, which allows an attacker to send a crafted HTTP request that triggers the installation of an MCP server, leading to RCE. Since MCPJam inspector by default listens on 0.0.0.0 instead of 127.0.0.1, an attacker can trigger the RCE remotely via a simple HTTP request. Version 1.4.3 contains a patch.

Patch / fix

  • npm @mcpjam/inspector 1.4.3
  • mcpjam inspector 1.4.3

Is CVE-2026-23744 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/multi/http/mcpjam_inspector_rce)
  2. Published

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
9mo ago

Exploit prediction

67.52% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm @mcpjam/inspector
<1.4.3
1.4.3

Affected products

  • MCPJam inspector

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.