UTC
Medium

Token Optimizer MCP: Unauthenticated Path Traversal in Dashboard Session Log API Endpoints

CVE-2026-55156 · GHSA-76pc-mqxp-3rq5 · published 2026-08-14

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
0.45%
Fixed in
5.1.0
  • Exploitation Public proof of concept
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

An unauthenticated remote attacker can read the contents of any .jsonl file accessible to the process running the dashboard server. In a typical deployment this includes all session log files (which contain tool invocations, hook outputs, and token usage data) as well as any other .jsonl file reachable via .. traversal from hooksDataPath. The constraint that the resolved path must end in .jsonl limits the attack surface to that file extension, but session logs can contain sensitive operational data. The same path traversal is present in both /api/session-summary and /api/session-events, and neither endpoint requires authentication.

What to do

Upgrade @ooples/token-optimizer-mcp to 5.1.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

1. Validate sessionId format before use: reject any value that does not match a strict allowlist such as /^[a-zA-Z0-9-]{1,64}$/. This prevents / and . characters from entering the path construction entirely. 2. Alternatively, apply path.basename to strip all directory components: path.basename(sessionId) reduces any traversal sequence to a bare filename before path.join. 3. Add authentication middleware to all /api/ routes so that even if a bypass is found the endpoints are not reachable without a valid session token.

Affected
PackageRegistryAffectedFixed in
@ooples/token-optimizer-mcpnpm< 5.1.05.1.0
Also in @ooples/token-optimizer-mcp
  1. HighToken Optimizer MCP: OS command injection in smart_user via username in get-user-info@ooples/token-optimizer-mcp

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].