{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-78378 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-78378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-78378 is a medium-severity vulnerability in ransomlook, published on 24 Aug 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-78378 and fix it if it is affected.\n\nWhat it is: CVE-2026-78378 is a medium-severity vulnerability in ransomlook, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-78378 in the wild and no public exploit code.\n\nAffected product: ransomlook. 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-78378/ (Markdown: https://insights.sbomify.com/CVE-2026-78378/index.md)","id":"CVE-2026-78378","markdown":"https://insights.sbomify.com/CVE-2026-78378/index.md","name":"CVE-2026-78378","record":{"aliases":["GHSA-mh87-9v73-ffwc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ransomlook web app","requires_auth":"none","summary":"Unauthenticated attackers can inject Redis glob patterns to enumerate private ransomware data via health and crypto endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Ransomlook contains a Redis glob pattern injection vulnerability caused by insufficient neutralization of user-controlled input before it is incorporated into Redis SCAN MATCH patterns.\n\nThe /api/health/\u003cname\u003e endpoint attempted to resolve the supplied name to a known group or market, but when resolution failed it fell back to using the attacker-controlled value directly in a Redis key pattern. An unauthenticated attacker could therefore supply Redis glob metacharacters such as *, ?, [ or ] to broaden the SCAN operation beyond the intended group. For example, requesting /api/health/* could enumerate health information, mirror slugs, and uptime series belonging to all groups and markets, including entities marked as private.\n\nSimilar unsafe interpolation was present in /api/crypto/chain/\u003cchain\u003e and in the delete_manual_torrent() function. The latter represents a potentially destructive sink because a crafted infohash containing glob metacharacters could cause the scan to match torrent-health keys belonging to other torrents if attacker-controlled input can reach that function.\n\nThe patch removes the unsafe fallback from the health endpoint and introduces glob escaping for user-controlled values before they are incorporated into Redis SCAN MATCH expressions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Redis Glob Pattern Injection Allows Unauthorized Enumeration of Private Ransomlook Data","id":"CVE-2026-78378","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":"Consent bypass in python_repl tool via batch kwargs forwarding in Amazon Strands Agents Tools","id":"CVE-2026-78379"},"packages":[],"prev":{"headline":"Open Redirect in Yordam Informatics's Library Automation System","id":"CVE-2026-78377"},"products":["ransomlook"],"published":"2026-08-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-24","vendors":["ransomlook"]},"summary":"Unauthenticated attackers can inject Redis glob patterns to enumerate private ransomware data via health and crypto endpoints.","url":"https://insights.sbomify.com/CVE-2026-78378/"}