dbcve.org
PraisonaiApplication · Praison

CVE-2026-40114

CRITICAL · 10.0 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 4.5.128 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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.128, the /api/v1/runs endpoint accepts an arbitrary webhook_url in the request body with no URL validation. When a submitted job completes (success or failure), the server makes an HTTP POST request to this URL using httpx.AsyncClient. An unauthenticated attacker can use this to make the server send POST requests to arbitrary internal or external destinations, enabling SSRF against cloud metadata services, internal APIs, and other network-adjacent services. This vulnerability is fixed in 4.5.128.

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

The /api/v1/runs endpoint in PraisonAI before version 4.5.128 accepts a webhook_url parameter in request bodies without any validation. An unauthenticated attacker can supply an arbitrary URL, causing the server to make HTTP POST requests to internal services (e.g., cloud metadata endpoints), external targets, or internal network resources when jobs complete.

MitigationUpgrade to PraisonAI version 4.5.128 or later which implements URL validation. If immediate patching is not possible, implement network-level controls to restrict outbound connections from the server and consider adding an application-layer allowlist for permitted webhook domains.

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.128

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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 The installed version is earlier than 4.5.128 (e.g., 4.5.100, 4.5.0, etc.)
  2. Identify if the API endpoint is exposed
    Check your server configuration or reverse proxy settings for routes exposing /api/v1/runs
    Affected if The /api/v1/runs endpoint is accessible from the network without authentication
  3. Test for missing webhook_url validation
    Send a POST request to /api/v1/runs with a webhook_url parameter pointing to an internal resource (e.g., http://169.254.169.254/latest/meta-data) and observe if the server attempts the request
    Affected if The endpoint accepts any URL in webhook_url without rejecting invalid or internal targets
  4. Review API request logging
    Examine server logs or traffic logs for POST requests made to arbitrary URLs that originated from the /api/v1/runs endpoint
    Affected if Outbound HTTP requests to unexpected internal or external domains appear in logs following API calls to /api/v1/runs

You are affected if PraisonAI version is below 4.5.128 AND the /api/v1/runs endpoint is accessible with a webhook_url parameter that is not validated, allowing the server to be directed to make requests to arbitrary URLs.

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 4.5.128 or later
Fixed in 4.5.128
Interim mitigation

Upgrade to PraisonAI version 4.5.128 or later which implements URL validation. If immediate patching is not possible, implement network-level controls to restrict outbound connections from the server and consider adding an application-layer allowlist for permitted webhook domains.

Recommended fix High confidence

4.5.128

  1. Check current PraisonAI version using pip show praisonai or your package manager
  2. Upgrade to version 4.5.128 or later using: pip install praisonai==4.5.128 or pip install --upgrade praisonai
  3. Verify the upgrade was successful by checking the installed version
  4. If using a requirements file, update the version constraint to praisonai>=4.5.128
  5. Restart any running PraisonAI services to ensure the patched version is loaded

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

Fix this in Praisonai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40114 — 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-40114 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