Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-55539 – Authentication Bypass (Unauthenticated Job Execution & Data Theft) – PraisonAI < 4.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-55539 is a missing authentication vulnerability (CWE-306) in PraisonAI, an open-source multi-agent teams framework. The framework’s asynchronous Jobs API endpoint (/api/v1/runs) is mounted without any authentication mechanism, allowing any network-reachable caller to submit jobs, read job results, cancel running operations, or delete jobs using the operator’s own LLM credentials. The issue carries a CVSS v3.1 base score of 8.6 (High) and is fixed in PraisonAI 4.6.58.

Technical details

  • Root cause: The create_app function in the praisonai/jobs/ module mounts the /api/v1/runs FastAPI router with no authentication middleware, no router-level dependency, and no per-route auth check — requests are accepted without any token, cookie, session identifier, or ownership validation.
  • Trigger conditions: The Jobs API server must be network-reachable by the attacker. It defaults to binding on 127.0.0.1, but exposure occurs when the service is bound publicly, run in a container, or placed behind a reverse proxy that forwards external traffic to it.
  • Attack vector: Network (AV:N) — no privileges and no user interaction are required (PR:N/UI:N).
  • Impact: An unauthenticated attacker can submit and execute arbitrary jobs against the operator’s LLM credentials, enumerate all jobs in the shared store, read other users’ job results, cancel in-progress operations, and delete completed jobs — resulting in low confidentiality and integrity impact and high availability impact (C:L/I:L/A:H).
  • Scope note: This is distinct from the earlier, related PraisonAI authentication issue (CVE-2026-44338), which only addressed the legacy Flask server; this flaw exists specifically in the newer FastAPI-based Jobs module and was not covered by that prior fix.

Affected software

  • PraisonAI (praisonai PyPI package), versions prior to 4.6.51 through builds up to 4.6.57 (i.e., all versions < 4.6.58)

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Mitigation and recommended actions

  • Immediate: Upgrade PraisonAI to version 4.6.58 or later, which introduces a PRAISONAI_JOBS_API_KEY authentication middleware requiring a valid Authorization or X-API-Key header on Jobs API requests.
  • If immediate patching is not possible:
    • Ensure the Jobs API service is bound only to 127.0.0.1/localhost and is never exposed via public network interfaces, container port mappings, or reverse proxies without an authenticating gateway in front of it.
    • Restrict network access to the Jobs API port using firewall rules or network segmentation, allowing only trusted internal callers.
    • Audit job history and stored results for evidence of unauthorized submissions, cancellations, or deletions if the service has been externally reachable.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge