CVE-2026-123135
Deferred Deferred - Pending Action

Hard-Coded Credentials in Dify Sandbox Run Handler

Publication date: 2026-11-05

Last updated on: 2026-11-05

Assigner: VulDB

Description
A vulnerability was found in langgenius dify up to 1.18.0/2.0.0-beta.2. Affected by this vulnerability is an unknown functionality of the file api/configs/feature/__init__.py of the component Sandbox Run Handler. The manipulation results in hard-coded credentials. The attack can be launched remotely. The exploit has been made public and could be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-05
Last Modified
2026-11-05
Generated
2026-11-06
AI Q&A
2026-11-05
EPSS Evaluated
N/A
NVD
CVE-2026-123135
EUVD
EUVD-2026-117723

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-259 The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a hardcoded default API key named 'dify-sandbox' in Dify's code-execution sandbox. The key is present in multiple configuration files and is used for authentication via the X-Api-Key header. Attackers can remotely execute arbitrary Python code by sending requests with this default key to the exposed sandbox endpoint on port 8194.

Detection Guidance

Check for exposed sandbox endpoints on port 8194 using network scanning tools like nmap. Inspect configuration files such as docker/.env.example and docker-compose.yaml for the hardcoded default API key 'dify-sandbox'. Verify if the sandbox endpoint is accessible externally by testing with curl commands like 'curl -H "X-Api-Key: dify-sandbox" http://<target-ip>:8194'.

Impact Analysis

An attacker could exploit this to run unauthorized code on your system, potentially stealing data, installing malware, or disrupting services. Since the default key is publicly known, no special knowledge is required to launch the attack. The sandbox's network access could allow lateral movement within your environment.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and access control. Hardcoded credentials violate security best practices and could lead to unauthorized data access, breaching GDPR's integrity and confidentiality principles or HIPAA's safeguards for protected health information.

Mitigation Strategies

Remove the hardcoded default API key 'dify-sandbox' from all configuration files. Replace it with a strong, unique secret. Ensure the sandbox port 8194 is not exposed externally by binding it to localhost only. Update to the latest version of Dify that includes the security patch.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-123135. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...