Secuno
ENNL
Book demo

CVE-2025-3466

Langgenius Dify vulnerability

7.2 HIGHPublic exploitEPSS 0.83%
  1. Published7 Jul 2025

Description

langgenius/dify versions 1.1.0 to 1.1.2 are vulnerable to unsanitized input in the code node, allowing execution of arbitrary code with full root permissions. The vulnerability arises from the ability to override global functions in JavaScript, such as parseInt, before sandbox security restrictions are imposed. This can lead to unauthorized access to secret keys, internal network servers, and lateral movement within dify.ai. The issue is resolved in version 1.1.3.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredHigh
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

Langgenius Dify≥ 1.1.0 < 1.1.3

Remediation

Fixed in
Langgenius Dify≥ 1.1.3

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-440089.8
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, the new method…
CVE-2026-440079.1
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.1, when a NodeVM is created…

Frequently asked

Is CVE-2025-3466 being actively exploited?

CVE-2025-3466 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.83%.

How severe is CVE-2025-3466?

CVE-2025-3466 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 0.83% probability of exploitation.

Which products are affected by CVE-2025-3466?

Affected products include Langgenius Dify.

How do I fix CVE-2025-3466?

Upgrade affected software to a fixed version, for example Langgenius Dify 1.1.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-3466 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.