Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

PraisonAI: Server-Side Request Forgery (SSRF) in SearxNG / search_web tools via attacker-controlled searxng_url parameter

CVE-2026-57143GHSA-4pcv-mg8v-vrgf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonaiagents 1.6.61), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L
EPSS
  • CVE-2026-57143: 0.27% estimated exploitation activity in the next 30 days; percentile 20.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) vulnerability in the SearxNG / searchweb search tools allows an attacker to make the server perform requests to arbitrary internal endpoints and read the responses back. The searxngurl argument is passed directly to requests.get() with no validation of scheme, host, or port. Because searxngurl is exposed to the LLM as a tool parameter and searchweb / searxngsearch are part of the default agent toolset, the vulnerability is reachable through prompt injection in any content an agent ingests (web pages, files, tool output). This enables reading internal services and APIs, internal host/port enumeration, and in cloud environments reachability of the instance metadata endpoint (169.254.169.254) with potential IAM/credential exposure. Details The SearxNG search provider performs no validation on the searxngurl argument before issuing the HTTP request. src/praisonai-agents/praisonaiagents/tools/searxngtools.py (lines 16–47): The same unvalidated…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4pcv-mg8v-vrgf

  2. Revision 1 · created ·

    Published from osv record GHSA-4pcv-mg8v-vrgf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57143

Advisory: PraisonAI: Server-Side Request Forgery (SSRF) in SearxNG / search_web tools via attacker-controlled searxng_url parameter
IDs: CVE-2026-57143, GHSA-4pcv-mg8v-vrgf
Record: https://patchnext.com/advisories/cve-2026-57143 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonaiagents 1.6.61. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonaiagents: affected < 1.6.61; fixed in 1.6.61

## Suggested inspection (read-only)
- `python -m pip show praisonaiagents`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonaiagents.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4pcv-mg8v-vrgf (OSV record GHSA-4pcv-mg8v-vrgf lists affected ranges: PyPI praisonaiagents >=0 <1.6.61 (fixed))
- Verified: https://github.com/advisories/GHSA-4pcv-mg8v-vrgf (GitHub-reviewed advisory GHSA-4pcv-mg8v-vrgf lists affected ranges: PyPI praisonaiagents >=0 <1.6.61)

Commands are suggestions: review each one before running it.

Loading voting…