Unauthenticated command execution via unchecked connect request
Published Jan 16, 2026 · Updated Jan 16, 2026
Missing authentication in MCPJam Inspector 1.4.2 and earlier allows remote attackers to execute commands through its HTTP connect API. The /api/mcp/connect route accepts command and args fields from request-controlled serverConfig data and launches the specified MCP server without authentication. Default binding to 0.0.0.0 exposes the route to any network-reachable attacker, who gains code execution with the Inspector process's privileges.
Summary
What happened
Missing authentication in MCPJam Inspector 1.4.2 and earlier allows remote attackers to execute commands through its HTTP connect API. The /api/mcp/connect route accepts command and args fields from request-controlled serverConfig data and launches the specified MCP server without authentication. Default binding to 0.0.0.0 exposes the route to any network-reachable attacker, who gains code execution with the Inspector process's privileges.
The record
- CVE
- CVE-2026-23744
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- MCPJam
- Product
- MCPJam Inspector
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA unauthenticated connect-request proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo