{"answers":{"affected":"1 open source package ship an affected version, including deluge. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25585 exists.","fix":"No fix has been published for CVE-2019-25585 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25585 is a medium-severity denial of service vulnerability in Dev Deluge, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25585 and fix it if it is affected.\n\nWhat it is: CVE-2019-25585 is a medium-severity denial of service vulnerability in Dev Deluge, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25585 exists.\n\nAffected packages and fixed versions:\n- deluge (PyPI): affected all versions up to 1.3.15; no fix listed\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-2019-25585/ (Markdown: https://insights.sbomify.com/CVE-2019-25585/index.md)","id":"CVE-2019-25585","markdown":"https://insights.sbomify.com/CVE-2019-25585/index.md","name":"CVE-2019-25585","record":{"aliases":["GHSA-mg6v-rx7x-h8q2","PYSEC-2026-38","UBUNTU-CVE-2019-25585"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BitTorrent client","requires_auth":"none","summary":"Local attackers can crash the Deluge BitTorrent client by inputting an excessively long string into the Webseeds field during torrent creation.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"deluge","vendor":"deluge-torrent"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1260","name":"Improper Handling of Overlap Between Protected Memory Ranges"}],"description":"Deluge 1.3.15 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the Webseeds field. Attackers can paste a buffer of 5000 bytes into the Webseeds field during torrent creation to trigger an application crash.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Deluge 1.3.15 Denial of Service via Webseeds Field","id":"CVE-2019-25585","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":1,"n_references":4,"next":{"headline":"Deluge 1.3.15 Denial of Service via URL Field","id":"CVE-2019-25586"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.3.15"],"package":"deluge","purl":"pkg:pypi/deluge","source":"PYSEC-2026-38"}],"prev":{"headline":"RarmaRadio 2.72.3 Server Field Buffer Overflow Denial of Service","id":"CVE-2019-25584"},"products":["Deluge"],"published":"2026-03-22","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2017-9031","kev_date_added":null,"published":"2017-05-17"},{"cvss_score":6.9,"headline":"Deluge 1.3.15 Denial of Service via URL Field","id":"CVE-2019-25586","kev_date_added":null,"published":"2026-03-22"},{"cvss_score":6.1,"headline":"Deluge Web-UI vulnerable to XSS through a crafted torrent file","id":"CVE-2021-3427","kev_date_added":null,"published":"2022-08-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["Dev"]},"summary":"Local attackers can crash the Deluge BitTorrent client by inputting an excessively long string into the Webseeds field during torrent creation.","url":"https://insights.sbomify.com/CVE-2019-25585/"}