LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-41948 is a critical Dify vulnerability where a user can break tenant boundaries and reach internal Plugin Daemon API paths. In practical terms, an attacker with easy account access may access or manipulate data outside their allowed workspace if they know a victim tenant UUID.

Executive priority

Treat as urgent for any internet-facing or multi-tenant Dify environment. The business risk is cross-tenant data exposure or manipulation in an AI application platform. Prioritize inventory, registration controls, and vendor patch tracking immediately.

Technical view

Dify v1.14.1 and prior insufficiently sanitize URL paths before forwarding requests to the Plugin Daemon internal REST API. Unencoded traversal sequences in task identifiers or manipulated filename parameters can escape the authorized tenant path and reach internal endpoints, including debug interfaces. The issue is tracked as CWE-23 path traversal.

Likely exposure

Organizations running Dify v1.14.1 or earlier are potentially exposed, especially multi-tenant deployments or environments allowing public sign-up. The source notes Dify Cloud permits free self-registration, reducing the barrier to account access.

Exploitation context

Public technical writeups and advisory references include exploit details. The supplied data does not show CISA KEV listing or confirmed active exploitation. Reported exploitation requires knowledge of a victim tenant UUID, while account creation may be trivial where self-registration is enabled.

Researcher notes

Evidence supports a path traversal in request forwarding to Plugin Daemon internal REST APIs. Do not assume a fixed release from the supplied sources; only a GitHub PR is cited. Validate with vendor commits, release notes, and deployment-specific exposure before closing.

Mitigation direction

  • Check vendor guidance and the linked Dify PR for the official fix status.
  • Upgrade Dify when a vendor-supported fixed version is available.
  • Disable or restrict public self-registration where business requirements allow.
  • Limit network exposure of Dify administrative and tenant-facing services.
  • Review access controls around Plugin Daemon internal API paths.

Validation and detection

  • Inventory Dify deployments and confirm versions at or below v1.14.1.
  • Determine whether public or low-friction account registration is enabled.
  • Review logs for unusual Plugin Daemon internal endpoint access attempts.
  • Check tenant isolation controls in staging after applying vendor updates.
  • Confirm remediation against vendor release notes or advisory updates.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-23: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41948 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-41948Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
langgeniusdify0affected
Weakness

CWE details

CWE-23

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-23 · source CWE mapping

Relative Path Traversal

Relative Path Traversal represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs