Is CVE-2026-123135 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123135 being exploited in the wild.

How severe is CVE-2026-123135?

Medium severity, with a CVSS score of 6.3, published 5 November 2026.

Which products and versions are affected?

Langgenius Dify up to 1.18.0 and 2.0.0-beta.2.

How is CVE-2026-123135 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-123135?

Check whether you run Langgenius Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-123135: langgenius dify hard-coded credentials in sandbox

CVE-2026-123135 · Severity: medium · CVSS 6.3 · Published 2026-11-05

Dify is a platform for building AI workflows and LLM applications. The code-execution sandbox component uses a default, trivially guessable API key ("dify-sandbox") for authentication, allowing remote attackers to bypass authentication and execute arbitrary code on the sandbox with no credentials required.

Technologies: Langgenius Dify. Vendors: Langgenius.

Quick answers

Is CVE-2026-123135 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123135 being exploited in the wild.
How severe is CVE-2026-123135?: Medium severity, with a CVSS score of 6.3, published 5 November 2026.
Which products and versions are affected?: Langgenius Dify up to 1.18.0 and 2.0.0-beta.2.
Is there a fix for CVE-2026-123135?: No fixed version is recorded yet. Change the CODE_EXECUTION_API_KEY and SANDBOX_API_KEY environment variables from the default value "dify-sandbox" to a strong, unique secret in docker/.env or your deployment configuration. Do not use the .env.example file directly for production without modifying these credentials.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-123135 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-123135?: Check whether you run Langgenius Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Change the CODE_EXECUTION_API_KEY and SANDBOX_API_KEY environment variables from the default value "dify-sandbox" to a strong, unique secret in docker/.env or your deployment configuration. Do not use the .env.example file directly for production without modifying these credentials.</anigation> </invoke>

Technical details

The vulnerability stems from hard-coded credentials (CWE-798) in the Sandbox Run Handler component (api/configs/feature/__init__.py), which authenticates API requests via the X-Api-Key header against a default public key "dify-sandbox". An attacker can remotely send requests with this known key to achieve unauthorized code execution. The default key is shipped in deployment examples and remains active unless explicitly changed by operators.

Affected products

langgenius dify up to 1.18.0 and 2.0.0-beta.2

Timeline

2026-07-02: disclosed: Privately reported via GitHub Security Advisory GHSA-hqjv-c67p-8hwv
2026-11-05: advisory
2026-10-16: other: Fix PR #44192 opened

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.