Quick answers
- Is CVE-2026-44335 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44335 being exploited in the wild.
- How severe is CVE-2026-44335?
- Critical severity, with a CVSS score of 9.8, published 8 May 2026.
- Which products and versions are affected?
- praisonaiagents (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.32.
- Is there a fix for CVE-2026-44335?
- Yes. praisonaiagents (PyPI): upgrade to 1.6.32 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44335 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44335?
- Check whether you run MervinPraison PraisonAI Agents, Praisonaiagents or praisonaiagents (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonaiagents (PyPI): upgrade to 1.6.32 or later
pip install "praisonaiagents>=1.6.32"
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in PraisonAI due to a differential in how URLs are parsed by the Python 'urlparse' library and the 'requests' library. The '_validate_url' function uses 'urlparse' to extract the hostname for security checks; however, 'urlparse' misinterprets backslashes in certain contexts (e.g., 'http://127.0.0.1\\@1.1.1.1'), identifying a public IP as the host. Conversely, the 'requests' library treats the backslash as a path character and connects to the internal IP (127.0.0.1). This allows an unauthenticated remote attacker to bypass internal network blocks and access local services. The issue is fixed in version 1.6.32.
Affected products
- MervinPraison praisonaiagents <= 1.6.31
Identifiers
- CVE-2026-44335
- GHSA-q9pw-vmhh-384g
- PYSEC-2026-2950
Timeline
- 2026-04-29: disclosed
- 2026-05-06: advisory
- 2026-05-08: other: NVD publication