{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1796 exists.","fix":"No fix has been published for CVE-2025-1796 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1796 is a high-severity vulnerability in langgenius/dify, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1796 and fix it if it is affected.\n\nWhat it is: CVE-2025-1796 is a high-severity vulnerability in langgenius/dify, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1796 exists.\n\nAffected product: langgenius/dify. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-1796/ (Markdown: https://insights.sbomify.com/CVE-2025-1796/index.md)","id":"CVE-2025-1796","markdown":"https://insights.sbomify.com/CVE-2025-1796/index.md","name":"CVE-2025-1796","record":{"aliases":["GHSA-cvg9-334x-w586"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Dify AI platform","requires_auth":"low_privilege","summary":"Attackers can predict password reset codes due to weak PRNG usage, enabling full account takeover including admin privileges in Dify.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"dify","vendor":"langgenius"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Weak cryptography in langgenius/dify","id":"CVE-2025-1796","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in Baiyiyun Asset Management and Operations System","id":"CVE-2025-1797"},"packages":[],"prev":{"headline":"Mishandling of comma during folding and unicode-encoding of email headers","id":"CVE-2025-1795"},"products":["langgenius/dify"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-56157","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":9.8,"headline":"Unsanitized Input in langgenius/dify","id":"CVE-2025-3466","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Misconfiguration in n/a","id":"CVE-2025-63386","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":9.1,"headline":"Misconfiguration in n/a","id":"CVE-2025-63388","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":8.8,"headline":"Code Injection in langgenius/dify","id":"CVE-2024-10252","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.1,"headline":"Authentication Bypass in langgenius/dify","id":"CVE-2024-12776","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8,"headline":"XSS Vulnerability in langgenius/dify","id":"CVE-2025-3467","kev_date_added":null,"published":"2025-07-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["langgenius"]},"summary":"Attackers can predict password reset codes due to weak PRNG usage, enabling full account takeover including admin privileges in Dify.","url":"https://insights.sbomify.com/CVE-2025-1796/"}