Skip to main content

Dify EUVD-2026-30772

| CVE-2026-41947 CRITICAL
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-05-18 VulnCheck GHSA-48v9-p8g8-55vg
9.3
CVSS 4.0
Share

CVSS VectorNVD

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

7
CVSS changed
May 26, 2026 - 17:22 NVD
9.1 (CRITICAL) 9.3 (CRITICAL)
Analysis Updated
May 18, 2026 - 15:29 vuln.today
v2 (cvss_changed)
Re-analysis Queued
May 18, 2026 - 15:22 vuln.today
cvss_changed
Severity Changed
May 18, 2026 - 15:22 NVD
HIGH CRITICAL
CVSS changed
May 18, 2026 - 15:22 NVD
7.4 (HIGH) 9.1 (CRITICAL)
Source Code Evidence Fetched
May 18, 2026 - 15:00 vuln.today
Analysis Generated
May 18, 2026 - 15:00 vuln.today

DescriptionNVD

Dify version 1.14.1 and prior 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.

AnalysisAI

Cross-tenant authorization bypass in LangGenius Dify versions through 1.14.1 lets any logged-in editor reroute another tenant's LLM trace traffic - including prompts and model responses - to an attacker-controlled observability provider. Because Dify Cloud permits free self-registration, the authentication barrier is effectively trivial; publicly available exploit code exists and a vendor patch is shipped via PR #35793. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Verify Dify deployment version and assess scope of multi-tenant isolation; implement enhanced logging on trace-configuration API endpoints to detect unauthorized modifications. Within 7 days: Apply vendor patch by upgrading Dify to a version after 1.14.1 that includes the authorization fix from PR #35793; audit and rotate any observability provider credentials configured in Dify trace settings. …

Sign in for detailed remediation steps.

Share

EUVD-2026-30772 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy