Skip to main content
VulnerabilityPublished Updated

CVE-2025-1796: langgenius/dify · PRNG

Affects langgenius/difySource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/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.10.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

  1. Immediately replace the use of Python's random.randint for generating password reset codes with a cryptographically secure PRNG, such as the secrets module (e.g., secrets.randbelow) or os.urandom.
  2. Restrict and monitor access to workflow tools that can expose PRNG outputs to minimize the risk of attackers obtaining the internal state.
  3. Implement multi-factor authentication (MFA) for all accounts, especially administrators, to reduce the impact of compromised reset codes.
  4. Conduct code audits and security reviews to identify and remediate other uses of weak PRNGs or insecure token generation.
  5. Deploy anomaly detection to identify unusual password reset requests or patterns indicative of exploitation attempts.
  6. Educate developers and security teams on cryptographic best practices to prevent recurrence.
  7. If possible, rotate all password reset tokens and force password resets after patching the vulnerability.
  8. Monitor threat intelligence sources for emerging exploits targeting this vulnerability and respond accordingly.

Description

A vulnerability in langgenius/dify v0.10.1 allows an attacker to take over any account, including administrator accounts, by exploiting a weak pseudo-random number generator (PRNG) used for generating password reset codes. The application uses `random.randint` for this purpose, which is not suitable for cryptographic use and can be cracked. An attacker with access to workflow tools can extract the PRNG output and predict future password reset codes, leading to a complete compromise of the application.

References

Community reviews

Loading reviews…