PraisonAI recipe serve Typer command bypasses the non-localhost authentication guard
Affects PraisonAI 4.5.112 through 4.6.58 when recipe serve is started with the deprecated Typer command on a non-localhost interface without --api-key. Fixed in 4.6.59.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 4.6.59
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
PraisonAI, a multi-agent teams system, is affected when its recipe server is started through the `praisonai recipe serve` command on a non-localhost interface. In that case the server runs without authentication, so anyone who can reach it could access the recipe API and, if enabled, the admin reload endpoint.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PraisonAI is a multi-agent teams system. From version 4.5.112 to before version 4.6.59, PraisonAI's installed console entrypoint is Typer-first. In current releases, the recipe command is registered in the Typer app and praisonai recipe serve dispatches to the deprecated Typer command in src/praisonai/praisonai/cli/commands/recipe.py. That Typer command can start the Recipe HTTP server on a non-localhost interface with no authentication. It prints a deprecation warning, and then launches the server. Because config.auth is absent, create_app() does not attach the API-key or JWT middleware. Unauthenticated requests can then reach the recipe API and, when enabled, /admin/reload. This issue has been patched in version 4.6.59.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- MervinPraison PraisonAI
From 4.5.112 · fixed in 4.6.59
- praisonaiPyPI
From 4.5.112 · fixed in 4.6.59
References 1
GitHub · MervinPraison/PraisonAI
Questions about CVE-2026-56836
What does this mean?
The deprecated Typer 'praisonai recipe serve' command can start the recipe HTTP server on a non-localhost interface with no authentication. Callers outside the local machine can then list recipes and trigger recipe validation or execution flows meant for local or authenticated callers. When admin endpoints are enabled, the admin reload endpoint is also reachable.Source: github.com
Am I affected, and how do I check?
Affected versions are PraisonAI 4.5.112 up to and including 4.6.58, and the praisonai package under the same ranges. The setup is the recipe server started through the Typer 'praisonai recipe serve' command with a non-localhost host binding and without --api-key, since authentication is only enabled when --api-key is passed. To check, look at the installed version (for example with 'pip show praisonai') and at the host and --api-key options used when the command was run.Source: github.com
What should I do about it?
Upgrade PraisonAI to version 4.6.59 or later, which is the listed fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data