Is CVE-2026-41948 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41948 being exploited in the wild.

How severe is CVE-2026-41948?

High severity, with a CVSS score of 7.7, published 18 May 2026.

Is there a fix for CVE-2026-41948?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-41948 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-41948?

Check whether you run Langgenius Dify 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.

CVE-2026-41948: LangGenius Dify path traversal in Plugin Daemon internal API

CVE-2026-41948 · Severity: high · CVSS 7.7 · Published 2026-05-18

Dify, an open-source platform for building AI applications, contains a security flaw in how it handles internal requests between its components. An attacker with a standard account can bypass security boundaries to access restricted internal interfaces, potentially leading to unauthorized data access or system manipulation. Because Dify Cloud allows anyone to register for a free account, this vulnerability is easily accessible to external actors.

Technologies: Langgenius Dify. Vendors: Langgenius.

Quick answers

Is CVE-2026-41948 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41948 being exploited in the wild.
How severe is CVE-2026-41948?: High severity, with a CVSS score of 7.7, published 18 May 2026.
Which products and versions are affected?: Langgenius Dify <= 1.14.1.
Is there a fix for CVE-2026-41948?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-41948 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41948?: Check whether you run Langgenius Dify 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.

Technical details

A path traversal vulnerability exists in Dify's `BasePluginClient._prepare_request` component due to insufficient sanitization of URL paths before they are forwarded to the Plugin Daemon's internal REST API. By using unencoded dot sequences (e.g., ".." or "%2e%2e") in task identifiers or filename parameters, an authenticated attacker can escape the authorized tenant path. This allows access to internal endpoints, such as debug interfaces, provided the attacker knows the target tenant's UUID. While the vulnerability requires authentication, the risk is elevated by the fact that Dify Cloud supports open self-registration. A fix involving path decoding and segment validation was introduced in pull request #35796.

Affected products

LangGenius Dify <= 1.14.1

Timeline

2026-05-05: other: Fix pull request submitted to GitHub
2026-05-18: disclosed: Vulnerability disclosed by VulnCheck and NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.