Skip to main content
VulnerabilityPublished Updated

CVE-2024-10252: langgenius/dify · Code Injection

Affects langgenius/difySource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublanggenius/difypkg:github/langgenius/difyOther threatsAffected
  • <=0.9.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-10252, European organizations should: 1) Immediately upgrade langgenius/dify to a patched version once available; in the absence of patches, consider disabling or isolating the Dify sandbox service. 2) Implement strict network segmentation and firewall rules to prevent unauthorized internal SSRF requests, limiting the sandbox’s ability to make outbound or internal network calls. 3) Harden the sandbox environment by enforcing least privilege principles, ensuring the sandbox runs with minimal permissions and cannot escalate to root. 4) Employ runtime application self-protection (RASP) or intrusion detection systems to monitor and block suspicious SSRF or code injection attempts. 5) Conduct thorough code reviews and penetration testing focused on SSRF and code injection vectors within the sandbox. 6) Monitor logs for unusual activity related to the sandbox service, such as unexpected Python code execution or deletion attempts. 7) Educate developers and security teams about the risks of improper code generation and sandbox escape techniques to prevent similar vulnerabilities in future development.

Description

A vulnerability in langgenius/dify versions <=v0.9.1 allows for code injection via internal SSRF requests in the Dify sandbox service. This vulnerability enables an attacker to execute arbitrary Python code with root privileges within the sandbox environment, potentially leading to the deletion of the entire sandbox service and causing irreversible damage.

References

Community reviews

Loading reviews…