Authentication Bypass in PraisonAI (CVE-2026-55533)
Summary
Authentication bypass in PraisonAI (CVE-2026-55533). Data can be tampered with by attackers. Exploitable via POST /v1/recipes/run. Mitigation: upgrade to 4.6.58 or later.
Original description
The description as published by the source.
PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, create_auth_middleware() allows requests when auth=api-key lacks PRAISONAI_API_KEY or JWT authentication lacks PRAISONAI_JWT_SECRET. An externally bound Recipe server can therefore accept unauthenticated POST /v1/recipes/run requests despite authentication being enabled. This issue is fixed in version 4.6.58.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55533 has been found in PraisonAI.
Attackers can target a specific entry point like POST /v1/recipes/run over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade PraisonAI to 4.6.58 or later.
If unsure, ask your IT team or search "PraisonAI CVE-2026-55533" on the vendor's site.
CVE-2026-55533 (PraisonAI) — CWE-287 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /v1/recipes/run / POST /v1/recipes/stream / POST /v1/recipes/validate / POST /admin/reload
Patched: 4.6.58 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in PraisonAI. Attackers reach the vulnerable code path via POST /v1/recipes/run without authentication.
Check the vendor advisory for the affected versions of PraisonAI. Attack surface: POST /v1/recipes/run / POST /v1/recipes/stream / POST /v1/recipes/validate / POST /admin/reload.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 4.6.58.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /v1/recipes/run requests with malformed payloads or SQL meta-characters. Run grep -r 'PraisonAI' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'PraisonAI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
PraisonAIを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /v1/recipes/run' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /v1/recipes/runへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade PraisonAI to 4.6.58ステージング環境で 4.6.58 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /v1/recipes/run on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com
- web github.com