Advisory

GHSA-j4f3-55x4-r6q2

Details, part 2 of 2. The advisory

Details

Severity

Suggested severity: Critical.

Rationale:

  • AV: exploitation is a direct HTTP JSON-RPC request.
  • AC: no race, user gesture, or special state is required.
  • PR: no credentials are required; invalid credentials are ignored.
  • UI: no user interaction is required after the server is running.
  • S: impact is within the authority of the MCP server process and its registered tools.
  • C: resources, prompts, and tool-returned data may expose sensitive data.
  • I: unauthenticated callers can drive server-side tools.
  • A: unauthenticated callers can invoke destructive or resource-consuming tools if registered.

Suggested Fix

Recommended minimum fix:

  1. Add security, auth, authRequired, apiKeys, or authorize(req) to MCPServerConfig.
  2. Fail closed for HTTP transport when auth is not configured, unless the caller explicitly opts into unauthenticated loopback-only development mode.
  3. Bind HTTP transport to 127.0.0.1 by default, or require an explicit host when binding to all interfaces.
  4. Call MCPSecurity.check(...) or equivalent middleware before every non-health POST request reaches handleRequest().
  5. Return 401 for missing or invalid credentials before dispatching initialize, tools/list, tools/call, resources/read, or prompts/get.
  6. Add Origin/Host protections for loopback HTTP transports to reduce DNS rebinding exposure.
  7. Add regression tests proving:
  • no-auth tools/list returns 401;
  • no-auth tools/call returns 401 and does not invoke the handler;
  • invalid bearer token returns 401;
  • valid bearer token invokes the handler;
  • default start({ port }) does not bind to all interfaces without an explicit opt-in.

Affected Package/Versions

  • Repository: MervinPraison/PraisonAI
  • Ecosystem: npm
  • Package: praisonai
  • Component: src/praisonai-ts/src/mcp/server.ts
  • Related unused security component: src/praisonai-ts/src/mcp/security.ts
  • Current npm version checked: 1.7.1
  • Refreshed origin/main checked: 1ad58ca02975ff1398efeda694ea2ab78f20cf3e

Confirmed affected range:

>= 1.5.0, <= 1.7.1

Boundary:

1.4.0 does not export MCPServer and does not ship dist/mcp/server.js.

No fixed npm version is known at the time of this report.

Version Sweep

The included sweep installs selected npm versions and checks the HTTP MCPServer path:

node poc/version_sweep_poc.js

Observed result:

1.4.0: mcpServerExported=false, hasDistMcpServer=false
1.5.0: mcpServerExported=true, hasDistMcpServer=true, noAuthToolCallInvoked=true, bindAddress=::
1.5.4: mcpServerExported=true, hasDistMcpServer=true, noAuthToolCallInvoked=true, bindAddress=::
1.6.0: mcpServerExported=true, hasDistMcpServer=true, noAuthToolCallInvoked=true, bindAddress=::
1.7.0: mcpServerExported=true, hasDistMcpServer=true, noAuthToolCallInvoked=true, bindAddress=::
1.7.1: mcpServerExported=true, hasDistMcpServer=true, noAuthToolCallInvoked=true, bindAddress=::

Advisory History

Known related public advisories:

  • GHSA-9mqq-jqxf-grvw / CVE-2026-44336: pip:praisonai MCP tools/call path traversal to RCE in Python praisonai mcp serve, affected <= 4.6.33.
  • CVE-2026-47394: pip:praisonai incomplete MCP path traversal fix affecting Python workflow/deploy handlers.
  • poc: deprecated Python MCP SSE Host/Origin/session issue.
  • poc: npm TypeScript AgentOS missing authentication.

This report is distinct because it targets:

  • ecosystem: npm;
  • package: praisonai;
  • component: src/praisonai-ts/src/mcp/server.ts;
  • root cause: TypeScript MCPServer HTTP transport missing auth and not using MCPSecurity;
  • primitive: unauthenticated and invalid-auth JSON-RPC tools/call invokes arbitrary registered TypeScript MCP tools; and
  • affected range: >= 1.5.0, <= 1.7.1.

The Python MCP advisories cover path traversal in specific Python MCP tool handlers. They do not cover the npm TypeScript MCPServer transport or its unwired security manager.

Sources & licences