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

CVE-2026-61430

HIGH · 8.5 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 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 1.6.78 contains a server-side request forgery vulnerability in the web_crawl tool that validates hostnames at check time but re-resolves them at connection time without IP pinning. Attackers can use DNS rebinding to bypass SSRF protection and retrieve internal HTTP response bodies from private or loopback services.

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

PraisonAI before 1.6.78 has an SSRF vulnerability in its web_crawl tool where hostname validation occurs at check time but DNS resolution happens again at connection time without IP pinning. Attackers exploit this via DNS rebinding to bypass the initial validation, causing the server to connect to internal/private IP addresses (e.g., 127.0.0.1, 192.168.x.x) and exfiltrate sensitive HTTP response bodies.

MitigationUpgrade to PraisonAI 1.6.78 or later. Alternatively, implement IP pinning by resolving the hostname to an IP at validation time and using that exact IP for the connection, preventing DNS rebinding attacks.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 if PraisonAI is installed
    Check for PraisonAI package installation via package manager or pip list, or locate the application directory
    Affected if PraisonAI is present on the system
  2. Determine installed PraisonAI version
    Run 'pip show praisonai' or check the package version in your Python environment, then compare to 1.6.78
    Affected if Version is below 1.6.78 (e.g., 1.6.77 or earlier)
  3. Check if web_crawl tool is accessible or configured
    Examine the PraisonAI configuration or codebase for web_crawl tool definitions and any web scraping/crawling functionality
    Affected if web_crawl tool is enabled or available for use
  4. Inspect hostname validation logic in web_crawl
    Review the source code of the web_crawl implementation for DNS rebinding protection - look for whether IP pinning is implemented at connection time
    Affected if No IP pinning is found; hostname is resolved separately at validation time and connection time without binding to the initially resolved IP
  5. Test for SSRF susceptibility via DNS rebinding
    If you have access to a test environment, configure the web_crawl tool with a controlled DNS name that resolves to internal IPs (127.0.0.1 or private range) and observe if connections succeed
    Affected if The tool successfully connects to internal/private IP addresses after initial hostname validation

You are affected if PraisonAI is installed with a version before 1.6.78 and the web_crawl tool is accessible, as the lack of IP pinning allows DNS rebinding to 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 1.6.78 or later. Alternatively, implement IP pinning by resolving the hostname to an IP at validation time and using that exact IP for the connection, preventing DNS rebinding attacks.

Recommended fix Moderate confidence

1.6.78

  1. Upgrade PraisonAI to version 1.6.78 or later to address the SSRF vulnerability in the web_crawl tool
  2. Verify the upgrade was successful by checking the installed version
  3. If upgrading is not immediately possible, consider disabling or restricting the web_crawl tool to trusted sources only

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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