{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32702 exists.","fix":"No fix has been published for CVE-2026-32702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32702 is a medium-severity vulnerability in Cleanuparr, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32702 and fix it if it is affected.\n\nWhat it is: CVE-2026-32702 is a medium-severity vulnerability in Cleanuparr, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32702 exists.\n\nAffected product: Cleanuparr. 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-2026-32702/ (Markdown: https://insights.sbomify.com/CVE-2026-32702/index.md)","id":"CVE-2026-32702","markdown":"https://insights.sbomify.com/CVE-2026-32702/index.md","name":"CVE-2026-32702","record":{"aliases":["GHSA-gjmf-m27r-2c9v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Media cleanup automation tool","requires_auth":"none","summary":"Unauthenticated attackers can enumerate valid usernames in Cleanuparr by measuring response time differences during login attempts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cleanuparr","vendor":"cleanuparr_project"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Cleanuparr is a tool for automating the cleanup of unwanted or blocked files in Sonarr, Radarr, and supported download clients like qBittorrent. From 2.7.0 to 2.8.0, the /api/auth/login endpoint contains a logic flaw that allows unauthenticated remote attackers to enumerate valid usernames by measuring the application's response time. It appears that the hashing function, which is the most time-consuming part of the process by design, occurs as part of the VerifyPassword function. With the short circuits occurring before the hashing function, a timing differential is introduced that exposes validity to the actor. This vulnerability is fixed in 2.8.1.","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":"Cleanuparr has Username Enumeration via Timing Attack","id":"CVE-2026-32702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy","id":"CVE-2026-32703"},"packages":[],"prev":{"headline":"Qwik has array method pollution in FormData processing, allowing type confusion and DoS","id":"CVE-2026-32701"},"products":["Cleanuparr"],"published":"2026-03-13","related":[],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["Cleanuparr"]},"summary":"Unauthenticated attackers can enumerate valid usernames in Cleanuparr by measuring response time differences during login attempts.","url":"https://insights.sbomify.com/CVE-2026-32702/"}