CVE-2026-44335
SSRF Bypass in PraisonAI Prior to 1.6.32
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| praison | praisonaiagents | to 1.6.32 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-44335 is a Server-Side Request Forgery (SSRF) vulnerability in PraisonAI versions prior to 1.6.32. The issue arises from a logical flaw in the URL validation logic where the function used to parse URLs (_validate_url) incorrectly interprets certain crafted URLs due to differences between the urlparse function and the requests library.
Specifically, an attacker can craft a URL like "http://127.0.0.1:6666\@1.1.1.1". The urlparse function treats the backslash as a normal character and the '@' as a delimiter, extracting the host as the public IP 1.1.1.1. However, the requests library treats the backslash as part of the path and connects to the internal address 127.0.0.1:6666. This discrepancy allows attackers to bypass SSRF protections and access internal resources.
This vulnerability was patched in PraisonAI version 1.6.32.
How can this vulnerability impact me? :
This SSRF vulnerability can allow attackers to bypass URL validation and make unauthorized requests to internal network resources that are normally inaccessible from outside. This can lead to exposure of sensitive internal services, data leakage, or further exploitation of internal systems.
Because the attacker can trick the system into connecting to internal IP addresses, they might gain access to internal APIs, databases, or other protected services, potentially compromising the confidentiality and integrity of your systems.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a logical flaw in URL validation that can be exploited by specially crafted URLs to bypass SSRF protections. Detection involves monitoring for suspicious URL patterns that include backslashes before an '@' symbol, such as URLs like http://127.0.0.1:6666\@1.1.1.1.
To detect potential exploitation attempts on your system or network, you can search logs or network traffic for URLs containing backslashes before '@' symbols.
- Use grep or similar tools to scan application logs for suspicious URLs: grep -r '\\@' /path/to/logs
- Monitor network traffic for requests containing backslash characters in URLs, for example using tcpdump or Wireshark with filters for '\\@'.
- Review application logs for requests to internal IP addresses that appear to be masked by such URL encoding tricks.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade PraisonAI to version 1.6.32 or later, where the URL validation logic flaw has been patched.
Until the upgrade can be applied, consider implementing additional input validation or filtering to reject URLs containing backslashes before '@' symbols or other suspicious patterns that could bypass SSRF protections.
Additionally, monitor and restrict outbound requests from the application to internal IP addresses to reduce the risk of SSRF exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the SSRF vulnerability in PraisonAI affects compliance with common standards and regulations such as GDPR or HIPAA.