LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41947: Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints

Dify before version 1.14.2 contains an authorization bypass vulnerability that allows authenticated editor users to set and enable trace configurations for any application regardless of tenant ownership. Attackers can exploit missing tenant ownership checks in the trace configuration endpoints to redirect all messages and responses from victim applications to attacker-controlled LLM trace providers. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.

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

Security readout for executives and security teams

Plain-English summary

Dify before 1.14.2 can let a user with editor-level access configure tracing for applications outside their tenant. That could silently send prompts, messages, and responses from another customer or workspace to an attacker-controlled trace provider. The issue is especially serious for multi-tenant or public-facing Dify environments.

Executive priority

Prioritize remediation urgently if Dify handles customer, business, or regulated AI data. The main business risk is silent cross-tenant data leakage through tracing. Upgrade and audit quickly; do not assume compromise without evidence from logs or vendor guidance.

Technical view

This is a CWE-639 authorization bypass in Dify trace configuration endpoints. Missing tenant ownership checks allow authenticated editor users to set and enable trace configurations for arbitrary applications. Sources describe redirection of victim application LLM traces to attacker-controlled providers. The CVE lists CVSS 4.0 score 9.3 and Dify versions before 1.14.2 as affected.

Likely exposure

Organizations running Dify before 1.14.2 are potentially exposed, especially multi-tenant deployments, externally reachable instances, or environments where users can self-register or obtain editor roles. The source notes Dify Cloud allows unauthenticated free self-registration, but customers should verify current vendor status.

Exploitation context

Public technical writeups are available, but the provided sources do not establish active exploitation in the wild. CISA KEV status is false in the provided bundle. The attack requires the ability to use an editor account, though account creation may be easy where self-registration is enabled.

Researcher notes

The affected surface is trace configuration authorization, not model inference itself. Validate exposure by version and by whether untrusted users can become editors. The CVSS vector lists PR:N, while the narrative describes authenticated editor users; treat this discrepancy carefully during risk scoring.

Mitigation direction

  • Upgrade Dify to version 1.14.2 or later.
  • Review Langgenius release notes, pull request, and patch commit.
  • Restrict self-registration and editor role assignment until upgraded.
  • Audit trace configurations for unexpected providers or destinations.
  • Assess possible exposure of prompts, responses, and sensitive application data.

Validation and detection

  • Inventory all Dify deployments and record their versions.
  • Flag any Dify instance below version 1.14.2.
  • Confirm the tenant ownership check patch is present.
  • Review trace settings across applications for unauthorized changes.
  • Check logs for unexpected trace configuration updates by editor users.
Prepared
Confidence
high
Sources
8

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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-41947 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.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

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
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical 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.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheck
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-41947Attack 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:N/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-639

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs