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

CVE-2026-6618

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A flaw has been found in langgenius dify up to 1.13.3. This issue affects the function parse_openai_plugin_json_to_tool_bundle of the file api/core/tools/utils/parser.py of the component ApiBasedToolSchemaParser. Executing a manipulation of the argument url can lead to server-side request forgery. The attack can be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Dify versions up to 1.13.3 contain a Server-Side Request Forgery (SSRF) vulnerability in the parse_openai_plugin_json_to_tool_bundle function within api/core/tools/utils/parser.py. The function accepts user-controlled input for the 'url' argument without proper validation, allowing an attacker to manipulate the API-based tool schema parser to make arbitrary HTTP requests to internal or external resources.

MitigationImplement strict URL validation and allowlisting for the url parameter in parse_openai_plugin_json_to_tool_bundle, restricting requests to permitted domains/IPs and preventing requests to internal network resources.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 Dify installation and version
    Check the running Dify version by inspecting the version file, Docker container labels, or API endpoint response (e.g., GET /console/api/api_keys or check deployment manifests)
    Affected if The installed Dify version is 1.13.3 or lower (any version up to and including 1.13.3)
  2. Locate the vulnerable parser.py file
    Search for the file api/core/tools/utils/parser.py in the Dify installation directory. Check if the function parse_openai_plugin_json_to_tool_bundle exists within it
    Affected if The file exists and contains the parse_openai_plugin_json_to_tool_bundle function, indicating the vulnerable code is present
  3. Verify API tool feature is accessible
    Check if the API-based tool schema parser functionality is accessible by examining if the /console/api/tools or related tool endpoints are exposed and functional in the environment
    Affected if Users with tool creation or import permissions can access the plugin/tool import functionality that calls the vulnerable function
  4. Check network exposure
    Review whether the Dify API server is exposed to untrusted networks (public internet or multi-tenant access) and whether tool import features are available to non-admin users
    Affected if The API is accessible to attackers who can supply arbitrary URLs to the tool schema parser
  5. Inspect request handling for URL parameter
    Examine the parse_openai_plugin_json_to_tool_bundle function code to confirm it accepts a 'url' parameter and makes HTTP requests without validation
    Affected if The function processes user-supplied URLs without proper allowlist validation before making HTTP requests

A user is affected if running any Dify version up to 1.13.3 where the vulnerable parser.py file exists and the tool import feature is accessible to attackers who can supply arbitrary URLs.

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

Implement strict URL validation and allowlisting for the url parameter in parse_openai_plugin_json_to_tool_bundle, restricting requests to permitted domains/IPs and preventing requests to internal network resources.

Recommended fix Moderate confidence

dify 1.14.0 or later (latest stable release)

  1. Identify your current dify version by checking the deployment configuration or docker-compose.yml
  2. Stop the dify services to prevent exposure during upgrade
  3. Backup your database and any persistent volumes
  4. Upgrade to dify 1.14.0 or later (the first version after 1.13.3 that should contain the fix)
  5. Verify the upgrade completed successfully
  6. Restart all dify services
  7. Test that the ApiBasedToolSchemaParser functionality works correctly with the updated version
  8. Monitor logs for any SSRF-related errors or unexpected outbound requests
Caveat Minor version upgrades in dify typically maintain backward compatibility but review release notes for any breaking changes to tool API schemas

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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