dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-60091

HIGH · 7.2 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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 before 4.6.78 contains an unauthenticated server-side request forgery vulnerability in the Jobs API /api/v1/runs endpoint. The webhook_url parameter is validated at request time but re-resolved at connection time, allowing attackers to use DNS rebinding to reach internal services with a blind SSRF attack.

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 · moderate confidence

PraisonAI before 4.6.78 has an unauthenticated SSRF vulnerability in the Jobs API /api/v1/runs endpoint where the webhook_url parameter undergoes initial validation but is re-resolved at connection time, enabling DNS rebinding attacks to bypass validation and access internal services via blind SSRF.

MitigationUpgrade to PraisonAI 4.6.78 or later which fixes the DNS rebinding vector by ensuring consistent validation at both request and connection time. Additionally, implement network segmentation and restrict outbound connections to prevent internal service access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Identify PraisonAI installation and version
    Run 'pip show praisonai' or check your package manager to find the installed version of PraisonAI
    Affected if The installed version is before 4.6.78 (e.g., 4.6.77, 4.6.70, etc.)
  2. Verify the Jobs API endpoint is exposed
    Check if your PraisonAI deployment exposes the /api/v1/runs endpoint (typically on port 8000 or configured port). Attempt a GET request to /api/v1/runs to confirm the endpoint is accessible.
    Affected if The /api/v1/runs endpoint returns a valid response (200/400/405) indicating it is reachable
  3. Confirm webhook_url parameter is accepted
    Send a POST request to /api/v1/runs with a test payload containing a webhook_url parameter (e.g., {"webhook_url": "http://example.com"}) and observe if it is processed
    Affected if The API accepts and processes the webhook_url parameter without rejecting it outright
  4. Check for internal network exposure
    Review network configuration to determine if the API is exposed to untrusted networks (public internet or guest networks) rather than being restricted to trusted internal users only
    Affected if The API is accessible from untrusted network segments

You are affected if your PraisonAI version is before 4.6.78 AND the /api/v1/runs endpoint is accessible to untrusted users, as the DNS rebinding attack against the webhook_url parameter can be exploited to perform blind SSRF against internal services.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PraisonAI 4.6.78 or later which fixes the DNS rebinding vector by ensuring consistent validation at both request and connection time. Additionally, implement network segmentation and restrict outbound connections to prevent internal service access.

Recommended fix High confidence

Upgrade to PraisonAI version 4.6.78 or later

  1. 1. Check current installed version of PraisonAI (e.g., pip show praisonai or check package.json)
  2. 2. Upgrade PraisonAI to version 4.6.78 or later using the appropriate package manager (e.g., pip install --upgrade praisonai or npm update)
  3. 3. Verify the upgrade was successful by checking the installed version
  4. 4. Test that the /api/v1/runs endpoint now properly validates webhook_url at connection time rather than allowing DNS rebinding

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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