dbcve.org
PraisonaiApplication · Praison

CVE-2026-39889

HIGH · 7.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to after 4.5.114 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PraisonAI is a multi-agent teams system. Prior to 4.5.115, the A2U (Agent-to-User) event stream server in PraisonAI exposes all agent activity without authentication. The create_a2u_routes() function registers the following endpoints with NO authentication checks: /a2u/info, /a2u/subscribe, /a2u/events/{stream_name}, /a2u/events/sub/{id}, and /a2u/health. This vulnerability is fixed in 4.5.115.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI's A2U (Agent-to-User) event stream server has a missing authentication vulnerability. The create_a2u_routes() function registers five endpoints (/a2u/info, /a2u/subscribe, /a2u/events/{stream_name}, /a2u/events/sub/{id}, and /a2u/health) without any authentication checks, allowing unauthenticated attackers to access all agent activity and event streams.

MitigationUpgrade PraisonAI to version 4.5.115 or later, which implements authentication on the A2U endpoints. If immediate patching is not feasible, restrict network access to these endpoints via firewall rules or a reverse proxy with authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PraisonaiApplication
Affected:<= 4.5.114

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI version
    Run 'pip show praisonai' or check your package manager to determine the installed version of praisonai
    Affected if Installed version is 4.5.114 or lower
  2. Verify A2U endpoints are exposed
    Attempt to access the following endpoints without authentication: /a2u/info, /a2u/subscribe, /a2u/events/{stream_name}, /a2u/events/sub/{id}, /a2u/health. Use curl or a browser to send unauthenticated requests to these routes.
    Affected if Any of these endpoints respond successfully without requiring authentication credentials
  3. Check if authentication middleware exists on A2U routes
    Inspect the source code of create_a2u_routes() function in the PraisonAI installation directory. Look for authentication decorators, middleware, or validation logic applied to these endpoints.
    Affected if No authentication checks are present in the code for the A2U endpoints
  4. Inspect network accessibility of A2U service
    Determine if the A2U server is listening on a network-accessible interface (0.0.0.0) rather than localhost only. Check configuration files or running service bindings.
    Affected if The A2U endpoints are reachable from non-localhost network addresses without authentication

A user is affected if their PraisonAI installation is version 4.5.114 or lower AND the A2U endpoints are accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.5.114
Interim mitigation

Upgrade PraisonAI to version 4.5.115 or later, which implements authentication on the A2U endpoints. If immediate patching is not feasible, restrict network access to these endpoints via firewall rules or a reverse proxy with authentication.

Recommended fix High confidence

4.5.115

  1. Upgrade PraisonAI to version 4.5.115 or later by running: pip install --upgrade praisonai or pip install praisonai==4.5.115

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Praisonai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39889 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data