Skip to main content

PraisonAI EUVDEUVD-2026-65522

| CVE-2026-55539 HIGH
Missing Authentication for Critical Function (CWE-306)
2026-08-25 https://github.com/MervinPraison/PraisonAI GHSA-2jgc-f764-c5r2
8.6
CVSS 3.1 · Vendor: https://github.com/MervinPraison/PraisonAI
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify exposed jobs API endpoint
  2. Delivery
    POST /api/v1/runs with attacker prompt
  3. Exploit
    Server executes against operator LLM credentials
  4. Execution
    Enumerate all jobs via GET /api/v1/runs
  5. Impact
    Exfiltrate tenant outputs via /{id}/result

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the PraisonAI jobs API to be network-reachable - the service defaults to binding 127.0.0.1, which prevents remote access without operator action. An operator must have explicitly changed the bind to 0.0.0.0 (via --host 0.0.0.0), published the container port, configured a reverse proxy forwarding to the jobs endpoint, or established a tunnel to the service. Once reachable, no special conditions apply: all seven /api/v1/runs endpoints accept unauthenticated requests with no token, cookie, API key, or session required. The in-memory store has no per-job ownership, so any caller can list, read results from, cancel, or delete any other caller's jobs without knowing a secret. Exploitation is further limited to PraisonAI versions prior to 4.6.58 running the FastAPI jobs module specifically; the separately patched Flask server (api_server.py, fixed at 4.6.34) is not affected.

Impact

CVSS 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H) is well-calibrated for this vulnerability. The High availability impact reflects unbounded job queuing with a default timeout of 3600 seconds per job, enabling direct consumption of the operator's LLM API credits and compute resources - financial harm is the realistic worst case for many deployments. Confidentiality is Low because attackers can enumerate and read all cross-tenant job outputs from the shared store, but cannot directly extract host secrets or persistent data beyond the in-memory jobs store. Integrity is Low because cancel and delete operations impair job lifecycle management without modifying underlying system state. The critical real-world limiting factor is network exposure: the default 127.0.0.1 bind prevents remote exploitation, and only operators who have actively exposed the service via --host 0.0.0.0, container port publishing, reverse proxy, or tunneling are at risk. No EPSS score was provided in the input data. No CISA KEV listing exists. However, working proof-of-concept code is documented in the vendor advisory, and the attack requires no sophistication beyond a single unauthenticated HTTP request - CVSS AC:L is appropriate. For organizations running PraisonAI with the jobs API exposed, priority should be HIGH, particularly due to LLM credit exhaustion risk.

Exploit ScenarioDerived

An attacker discovers a PraisonAI jobs API bound to a public interface (via --host 0.0.0.0 or container port publish) and sends a single unauthenticated POST http://TARGET:8005/api/v1/runs with JSON body {"prompt": "attacker-controlled content", "timeout": 3600} - the server responds HTTP 202 and queues the prompt for execution against the operator's LLM credentials with no challenge. The attacker then calls GET /api/v1/runs to enumerate all jobs across all tenants and iterates GET /api/v1/runs/{id}/result to exfiltrate private agent outputs from other users' sessions. Proof-of-concept confirming all five operations with zero credentials is documented in GHSA-2jgc-f764-c5r2.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 25, 2026

PraisonAI's async Jobs API FastAPI service exposes all seven /api/v1/runs endpoints - submit, list, status, result, cancel, delete, and stream - with zero authentication on every route, allowing any network-reachable caller to execute arbitrary prompts against the operator's configured LLM credentials and enumerate or exfiltrate cross-tenant job outputs. Publicly available exploit code is documented in GHSA-2jgc-f764-c5r2, with all five attack primitives confirmed via proof-of-concept returning HTTP 202/200/204 with no credentials. This is a distinct, unpatched sibling of CVE-2026-44338 - the Flask server fix at 4.6.34 did not touch the FastAPI jobs module, which remained fully unauthenticated through version 4.6.51.

RemediationAI

Upgrade PraisonAI to version 4.6.58 or later, which introduces authentication controls for the jobs server per commit 2f9677abb2ea68eab864ee8b6a828fd0141612e1 (https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1). The full release is available at https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58. If an immediate upgrade is not feasible, the highest-priority compensating control is to verify the jobs API binds only to localhost (--host 127.0.0.1, the default) and enforce firewall or container network policy rules blocking all external traffic to the jobs port (default 8005). Remove any --host 0.0.0.0 launch flags, revoke container port publish rules for port 8005, and audit all reverse proxy configurations for paths forwarding to the jobs endpoint. If multi-client access is required before upgrading, place an authenticating reverse proxy (e.g., nginx with auth_basic or an API gateway with Bearer token enforcement) in front of the jobs service as an interim measure - this adds an external auth layer without modifying the application but introduces a separate credential management dependency. The advisory (GHSA-2jgc-f764-c5r2) further recommends adding per-job ownership scoping and regression tests asserting unauthenticated requests return HTTP 401.

Affected VersionsENISA

PraisonAI < 4.6.58

Affected Packages

pypi praisonai fix: 4.6.58

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-306 (Missing Authentication for Critical Function). The FastAPI application in praisonai/jobs/server.py configures only CORSMiddleware before mounting the jobs router - CORS is a browser same-origin control enforced by the client, not server-side authentication. The APIRouter in router.py registers all routes under /api/v1/runs with no dependencies=[Depends(...)] at the router or individual route level. The sole Header(...) parameter present anywhere in the module, Idempotency-Key, is a request deduplication mechanism only. The in-memory job store contains no owner, principal, or session-binding field; list_jobs() returns the entire global store filtered only by caller-supplied status and session_id query parameters, enabling cross-tenant enumeration. A repository-wide grep of jobs/ for Depends, verify, token, authorization, bearer, x-api-key, HTTPBearer, AUTH_ENABLED, and check_auth returns only the string Authorization inside the CORS allow_headers list - confirming no authentication primitive exists in the module. Affected package: pkg:pip/praisonai, versions prior to 4.6.58.

Know when Python gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (https://github.com/MervinPraison/PraisonAI) PRIMARY 8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
vuln.today AI 8.6 HIGH

PR:N confirmed by complete absence of any auth primitive; A:H for unbounded LLM credit exhaustion via 3600s timeout jobs; C:L and I:L for cross-tenant read and cancel/delete.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/MervinPraison/PraisonAI).

CVSS VectorVendor: https://github.com/MervinPraison/PraisonAI

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

DescriptionCVE.org

Summary

PraisonAI's async Jobs API (the FastAPI service in praisonai/jobs/) installs its router with no authentication middleware, no router-level dependency, and no per-route auth check. Any caller who can reach the jobs server can submit agent jobs (executed against the operator's configured LLM credentials), list every job in the shared store, read other jobs' results, cancel running jobs, and delete terminal jobs - with no token, cookie, session, or per-job ownership value.

The server's default bind is 127.0.0.1, so remote reach requires an operator to bind a public interface, container-publish, reverse-proxy, or tunnel the service. Once reachable, the primitive is fully pre-authenticated.

This is a distinct, still-unpatched sibling of CVE-2026-44338. That CVE (GHSA-6rmh-7xcm-cpxj, fixed in 4.6.34) covered only the *legacy Flask* server src/praisonai/api_server.py. The fix added AUTH_ENABLED/AUTH_TOKEN/check_auth() to that file and did not touch the FastAPI jobs module. At the latest commit (9fcac3a, version 4.6.51) the legacy Flask server is patched but the jobs API remains completely unauthenticated.

Technical Detail

Source-to-sink trace

The FastAPI app includes the jobs router with only CORS middleware - no auth (server.py, create_app):

python
# src/praisonai/praisonai/jobs/server.py
def create_app(store=None, executor=None, cors_origins=None) -> FastAPI:
    app = FastAPI(title="PraisonAI Jobs API", ...)
# ... CORS middleware only (allow_headers includes "Authorization",
#     but CORS is not authentication) ...
    jobs_router = create_router(get_store(), get_executor())
    app.include_router(jobs_router)
# no dependencies=[Depends(...)]

The router (built inside create_router()) registers every job operation with no auth dependency. The only Header(...) parameter anywhere is the Idempotency-Key, which is deduplication, not authorization:

python
# src/praisonai/praisonai/jobs/router.py
router = APIRouter(prefix="/api/v1/runs", tags=["jobs"])

@router.post("",          status_code=202)  async def submit_job(request, response, body, idempotency_key=Header(None, alias="Idempotency-Key")): ...
@router.get("")                              async def list_jobs(status=None, session_id=None, page=1, page_size=20): ...
@router.get("/{job_id}")                     async def get_job_status(job_id): ...
@router.get("/{job_id}/result")              async def get_job_result(job_id): ...
@router.post("/{job_id}/cancel")             async def cancel_job(job_id): ...
@router.delete("/{job_id}", status_code=204) async def delete_job(job_id): ...
@router.get("/{job_id}/stream")              async def stream_job(job_id): ...

submit_job() builds a Job from attacker-controlled JSON and submits it. The executor saves and schedules it, and for the default praisonai framework runs the attacker prompt against a real agent:

python
# executor.py - submit() -> _execute_job() -> _run_agent() -> _run_praisonai_agents()
agent = Agent(instructions="You are a helpful AI assistant.", output="minimal")
result = await asyncio.to_thread(agent.start, job.prompt)
# attacker-controlled prompt

The in-memory store has no owner / principal / user concept. list_jobs() returns the whole store filtered only by caller-supplied status/session_id:

python
# store.py
async def list_jobs(self, status=None, session_id=None, limit=20, offset=0):
    jobs = list(self._jobs.values())
# global; no owner binding
    if session_id: jobs = [j for j in jobs if j.session_id == session_id]
    ...

A repository-wide grep of jobs/ for Depends|verify|token|authorization|bearer|x-api-key|HTTPBearer|AUTH_ENABLED|check_auth returns only the string "Authorization" inside the CORS allow_headers list. There is no authentication primitive in the module.

Distinction from CVE-2026-44338 (critical for triage)

CVE-2026-44338 (already fixed)This finding
ComponentLegacy Flask src/praisonai/api_server.pyFastAPI praisonai/jobs/
EndpointsGET /agents, POST /chat/api/v1/runs (submit/list/get/result/cancel/delete/stream)
Root causeAUTH_ENABLED=False, AUTH_TOKEN=None, no-op check_auth()No auth dependency, middleware, or token exists at all
Status at 4.6.51Patched (auth enabled by default, token auto-generated, secrets.compare_digest)Unpatched

The 4.6.34 remediation hardened only the Flask file. The jobs module is a separate code path that the fix did not reach.

Trigger conditions

  1. Start the server, e.g. python -m uvicorn praisonai.jobs.server:create_app --port 8005 --factory.
  2. Make it reachable (--host 0.0.0.0, container publish, reverse proxy, tunnel).
  3. Send unauthenticated requests to POST/GET /api/v1/runs, GET /api/v1/runs/{id}, GET /api/v1/runs/{id}/result, POST /api/v1/runs/{id}/cancel, DELETE /api/v1/runs/{id}.

Proof of Concept

Verified dynamically by running the real praisonai.jobs router, executor, and store over HTTP via FastAPI TestClient. The only stub is praisonaiagents.Agent (its .start() returns canned text), so no real LLM call and no API credentials were used. Every request below was sent with no Authorization header, cookie, or token (the runner asserts Authorization sent: None on each).

## Unauth POST /api/v1/runs (submit job)
   POST /api/v1/runs            -> HTTP 202   Authorization sent: None
   body: {"job_id":"run_de282b4c3f1c","status":"queued", ...}
## Unauth GET /api/v1/runs (list every job in shared store)
   GET /api/v1/runs             -> HTTP 200   Authorization sent: None
   body: {"jobs":[{"job_id":"run_de282b4c3f1c","status":"succeeded", ...}], "total":1, ...}
## Unauth GET /api/v1/runs/{id}/result (read tenant output)
   GET /api/v1/runs/.../result  -> HTTP 200   Authorization sent: None
   body: {"result":"TENANT-PRIVATE-OUTPUT for prompt='attacker-controlled job'", ...}
## Unauth POST /api/v1/runs/{id}/cancel (cancel a RUNNING job)
   t=0.0s status=running ... t=2.0s status=running
   POST /api/v1/runs/.../cancel -> HTTP 200   Authorization sent: None
   after cancel status=cancelled
## Unauth DELETE /api/v1/runs/{id} (delete terminal job)
   DELETE /api/v1/runs/...       -> HTTP 204   Authorization sent: None

Each privileged operation succeeded with zero credentials. (The result endpoint returns a different job's stored output - the cross-job confidentiality primitive.)

Equivalent trigger in a fully installed, network-exposed deployment

bash
python -m uvicorn praisonai.jobs.server:create_app --host 0.0.0.0 --port 8005 --factory

curl -sS -X POST http://TARGET:8005/api/v1/runs \
  -H 'Content-Type: application/json' \
  --data-binary '{"prompt":"attacker controlled job","timeout":3600}'
curl -sS http://TARGET:8005/api/v1/runs
curl -sS http://TARGET:8005/api/v1/runs/<job_id>/result
curl -sS -X POST http://TARGET:8005/api/v1/runs/<job_id>/cancel
curl -sS -X DELETE http://TARGET:8005/api/v1/runs/<job_id>

Impact

  • Execution / cost: unauthenticated callers run arbitrary prompts against the operator's configured LLM credentials, and can queue long-running jobs (up to timeout, default 3600s) consuming CPU, memory, queue slots, and provider billing.
  • Confidentiality: callers list all jobs (GET /api/v1/runs) and read completed results from the shared store - other callers' agent outputs.
  • Integrity / control: callers cancel running jobs and delete terminal jobs.

The realistic worst case is a reachable jobs endpoint used to run unauthorized prompts on the operator's LLM account, then enumerate and exfiltrate other jobs' outputs.

Suggested Mitigation

Mirror the fix already applied to the legacy Flask server (CVE-2026-44338), but for the jobs router:

  • Add a jobs-server auth token (e.g. PRAISONAI_JOBS_API_TOKEN) and require it on every /api/v1/runs route via a router-level dependency, so future routes inherit protection by default.
  • Use constant-time comparison (hmac.compare_digest / secrets.compare_digest).
  • Add per-job ownership / scoped job tokens so one caller cannot list, read, cancel, or delete another caller's jobs.
  • Keep 127.0.0.1 as default; warn or refuse when binding a public interface without auth configured.
  • Regression tests asserting unauthenticated POST / GET / cancel / delete return 401 when auth is enabled.
python
import hmac, os
from fastapi import Depends, Header, HTTPException

def verify_jobs_token(authorization: str | None = Header(None),
                      x_api_key: str | None = Header(None, alias="X-API-Key")):
    expected = os.getenv("PRAISONAI_JOBS_API_TOKEN")
    if not expected:
        raise HTTPException(401, "Jobs API auth is not configured")
    token = x_api_key
    if authorization and authorization.startswith("Bearer "):
        token = authorization[7:]
    if not token or not hmac.compare_digest(token, expected):
        raise HTTPException(401, "Unauthorized")
# create_router(...) -> APIRouter(prefix="/api/v1/runs", dependencies=[Depends(verify_jobs_token)])

Executive ViewAI

Why It Matters

PraisonAI's job scheduling API (versions through 4.6.51) is exposed without authentication to anyone with network access, enabling attackers to execute arbitrary AI prompts using your organization's LLM credentials and steal job data across all tenants. This creates direct exposure to fraudulent LLM API charges, compromise of LLM services, and potential exfiltration of sensitive data processed through your AI workflows.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% exploitable
Prevalence
Low
niche Python AI agent framework, limited enterprise footprint
Threat Intel
1
1 source
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Python

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2025-27520 CRITICAL POC
9.8 Apr 04

BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser

CVE-2025-2945 CRITICAL POC
9.9 Apr 03

pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi

CVE-2013-5093 MEDIUM POC
6.8 Sep 27

The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python

CVE-2025-32375 CRITICAL POC
9.8 Apr 09

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2024-21644 HIGH POC
7.5 Jan 08

pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.

CVE-2026-33017 CRITICAL POC
9.3 Mar 17

Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301

CVE-2017-9462 HIGH POC
8.8 Jun 06

In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse

CVE-2026-49869 CRITICAL POC
10.0 Jun 26

Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to

CVE-2026-39987 CRITICAL POC
9.3 Apr 08

Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/

CVE-2024-21645 MEDIUM POC
5.3 Jan 08

pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy