# CVE-2026-41948: Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access

> Authenticated attackers can traverse directories to access internal Plugin Daemon endpoints and debug interfaces, exposing sensitive data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-h666-98mq-949j

## What is CVE-2026-41948?

CVE-2026-41948 is a critical path traversal vulnerability in langgenius dify, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dify version 1.14.1 and prior contain a path traversal vulnerability that allows authenticated users to manipulate requests forwarded to the Plugin Daemon's internal REST API by exploiting insufficient URL path sanitization. Attackers can traverse out of their authorized tenant path using unencoded dot sequences in task identifiers or manipulated filename parameters to access internal endpoints such as debug interfaces, requiring only knowledge of the victim tenant's UUID. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-41948?

It affects 1 product.


Products: Dify Dify.

## How do I fix CVE-2026-41948?

No fix has been published for CVE-2026-41948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41948 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41948 exists.

Public exploit code:

- Dify <=1.14.1 - Unauthenticated Plugin Daemon Path Traversal (nuclei): http/cves/2026/CVE-2026-41948.yaml

## Other vulnerabilities in langgenius dify

- [CVE-2026-41947](https://insights.sbomify.com/CVE-2026-41947/): Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints (critical 9.3)
- [CVE-2025-0185](https://insights.sbomify.com/CVE-2025-0185/): Pandas Query Injection in langgenius/dify (high 8.8)
- [CVE-2026-61461](https://insights.sbomify.com/CVE-2026-61461/): Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text (high 8.7)
- [CVE-2025-67732](https://insights.sbomify.com/CVE-2025-67732/): Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint (high 8.4)
- [CVE-2026-41949](https://insights.sbomify.com/CVE-2026-41949/): Dify < 1.14.2 Authorization Bypass via File Preview Endpoint (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41948 and fix it if it is affected.

What it is: CVE-2026-41948 is a critical path traversal vulnerability in langgenius dify, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41948 exists.

Affected product: langgenius dify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41948/ (Markdown: https://insights.sbomify.com/CVE-2026-41948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41948
- OSV: https://osv.dev/vulnerability/CVE-2026-41948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41948/
Summaries are generated and may contain mistakes; the official description above is the record.