Skip to content

AAK-MCP-PRAISONAI-CVE-2026-61427-001: PraisonAI MCP unauthenticated-default + path traversal (below 4.6.78)

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
PraisonAiMcpNoAuthDefault

What it detects

PraisonAI before 4.6.78 exposes the MCP HTTP-stream transport without authentication by default: praisonai mcp serve --transport http-stream defaults --api-key to None and only enforces Authorization/Bearer checks when a key is configured, so an unauthenticated client can initialize a session, enumerate tools (tools/list), and invoke them (tools/call); arguments are also forwarded without validating the advertised inputSchema (CVE-2026-61427, CVSS 7.3). The same pin also covers CVE-2026-47394 — an arbitrary-file-read path traversal via workflow.show (and the dispatcher's unvalidated **kwargs from tools/call), an incomplete prior path-handling fix that was fully closed only in 4.6.40. The same floor also covers CVE-2026-48168 (CVSS 10, fixed 4.6.40): a command injection in PraisonAI's bundled Claude GitHub Actions workflow that splices an attacker-controlled pull-request branch name into a Bash run: block, with any @claude comment able to trigger the job, so a fork PR reaches arbitrary execution in the Actions runner. The 4.6.78 floor is the highest of the three, so a project pinned below it is exposed to all of them. CVE-2026-61438 (CVSS 7.3, GHSA-26mh-57q7-jfvr) names the same 4.6.78 as its fix: the job-workflow executor's AST sandbox lets the inline script: step of a YAML workflow run with PRAISONAI_ALLOW_JOB_WORKFLOWS=true reach os. No published release fixes it, so this rule reports it below 4.6.78 and a presence-only rule of its own reports the releases from 4.6.78. Default bind is 127.0.0.1, so remote reach needs a network bind. Treat < 4.6.78 (and unpinned) as exposed.

How to fix

Upgrade praisonai to >= 4.6.78 and pin it. Always configure --api-key for the HTTP-stream transport and never bind it to a non-loopback interface without authentication. For CVE-2026-61438 an upgrade is not enough, since every later release still ships the job-workflow executor: leave PRAISONAI_ALLOW_JOB_WORKFLOWS unset unless every workflow file it runs is trusted.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-PRAISONAI-CVE-2026-61427-001

Limitations

Reads praisonai in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock and uv.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. The dependency is not read when it is declared in a sub-directory manifest (services/api/pyproject.toml) or in a lockfile format the reader does not parse (pdm.lock). CVE-2026-61438 is read here below 4.6.78, as its advisory scopes it. No release fixed it: PyPI has no 4.6.78 (4.6.81 follows 4.6.77), and 4.6.81 to 4.7.24 ship the same _exec_inline_python, from 4.6.103 through the required praisonai-code. Those releases are reported for it by a presence-only rule of their own, so a reference that states no version, or a range that admits releases on both sides of 4.6.78, gets both rules' findings. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-PRAISONAI-CVE-2026-61427-001.md: the page then shows that text, with the registry reference appended under it.