Cyber Resilience

CVE-2026-40114

SSRF in Praisonai ≤ 4.5.128

Public PoCSSRF
Published
09 April 2026
Modified
17 April 2026
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS Score 0.0028 20th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2026-40114 is a high-severity SSRF (CWE-918) vulnerability in Praison Praisonai. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-40114 is a server-side request forgery (SSRF) vulnerability in PraisonAI, a multi-agent teams system. In versions prior to 4.5.128, the /api/v1/runs endpoint accepts an arbitrary webhook_url in the request body without any URL validation. Upon completion of a submitted job, whether successful or failed, the server uses httpx.AsyncClient to make an HTTP POST request to the specified URL, allowing requests to unintended destinations.

An unauthenticated attacker can exploit this vulnerability over the network with low complexity and no user interaction required. By submitting a job via the endpoint with a malicious webhook_url, the attacker causes the server to send POST requests to arbitrary internal or external targets when the job finishes. This enables SSRF attacks against cloud metadata services, internal APIs, and other network-adjacent services, with a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) reflecting low confidentiality and integrity impacts in a changed scope.

The vulnerability, associated with CWE-918 (Server-Side Request Forgery), is fixed in PraisonAI version 4.5.128. Security practitioners should upgrade to this version or later. Additional details are available in the GitHub Security Advisory at https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-8frj-8q3m-xhgm.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34936Same product: Praison Praisonai
CVE-2026-40157Same product: Praison Praisonai
CVE-2026-35615Same product: Praison Praisonai
CVE-2026-39306Same product: Praison Praisonai
CVE-2026-40315Same product: Praison Praisonai
CVE-2026-39308Same product: Praison Praisonai
CVE-2026-34934Same product: Praison Praisonai
CVE-2026-39307Same product: Praison Praisonai
CVE-2026-39305Same product: Praison Praisonai
CVE-2026-34952Same product: Praison Praisonai

Affected Assets

praison
praisonai
≤ 4.5.128

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References