CVE-2025-3466: Unsanitized input vulnerability in langgenius/dify code node
Dify
Versions 1.1.0 to 1.1.2 of langgenius/dify are vulnerable to arbitrary code execution through unsanitized input in the code node. The issue is resolved in version 1.1.3.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 42% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 7 Jul 2025
- last update
- 7 Jul 2025
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2025-07-07CVE-2025-3466: langgenius/dify versions 1.1.0 to 1.1.2 are vulnerable to unsanitized input in the code node, allowing execution of arbitrary…NVD · nvd.nist.gov/vuln/detail/CVE-2025-3466
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 7 Jul 2025 · first reported 7 Jul 2025
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2025-3466: Unsanitized input vulnerability in langgenius/dify code node https://gcdradar.vercel.app/incidents/cve-2025-3466-unsanitized-input-vulnerability-in-langgenius · AIR-2025-0438 · closed 2025-07-07 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-07-07 - AI role: Attack on AI - Products: Dify - CVE ids: CVE-2025-3466 - CVSS: 9.8 ## Summary Versions 1.1.0 to 1.1.2 of langgenius/dify are vulnerable to arbitrary code execution through unsanitized input in the code node. The issue is resolved in version 1.1.3. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-07-07: CVE-2025-3466: langgenius/dify versions 1.1.0 to 1.1.2 are vulnerable to unsanitized input in the code node, allowing execution of arbitrary… (https://nvd.nist.gov/vuln/detail/CVE-2025-3466) ## Sources - 2025-07-07 NVD: CVE-2025-3466: langgenius/dify versions 1.1.0 to 1.1.2 are vulnerable to unsanitized input in the code node, allowing execution of arbitrary… https://nvd.nist.gov/vuln/detail/CVE-2025-3466 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed6.1Dify CVE-2025-49149: Cross-site scripting vulnerability in Dify
Patch now · Disclosed · since 17 Jun 2025 · CVE-2025-49149
AI - closed9.8Dify CVE-2025-56157: Default database credentials present in Dify configuration
Patch now · Disclosed · since 18 Dec 2025 · CVE-2025-56157
AI - closed9.1Dify CVE-2025-63386: CORS misconfiguration vulnerability in Dify setup endpoint
Patch now · Disclosed · since 18 Dec 2025 · CVE-2025-63386
AI - closed9.1Dify CVE-2025-63388: CORS misconfiguration in Dify console system features endpoint
Patch now · Disclosed · since 18 Dec 2025 · CVE-2025-63388
AI - closed7.5Dify CVE-2025-63387: Insecure permissions in Dify system features endpoint
Patch now · Disclosed · since 18 Dec 2025 · CVE-2025-63387
AI - closed6.1Dify CVE-2025-58747: Cross-site scripting vulnerability in Dify MCP OAuth component
Patch now · Disclosed · since 17 Oct 2025 · CVE-2025-58747
AI