{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-78386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-78386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-78386 is a high-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-78386 and fix it if it is affected.\n\nWhat it is: CVE-2026-78386 is a high-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-78386 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-78386/ (Markdown: https://insights.sbomify.com/CVE-2026-78386/index.md)","id":"CVE-2026-78386","markdown":"https://insights.sbomify.com/CVE-2026-78386/index.md","name":"CVE-2026-78386","record":{"aliases":["GHSA-6q5p-jgh6-cxqm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RansomLook API","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive scraping credentials and bypass logic via RansomLook API, potentially enabling credential replay and evasion of anti-bot protections.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/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 exposed sensitive operator-side scraping configuration through multiple unauthenticated API responses. Location records associated with ransomware groups and markets were returned largely verbatim to unauthenticated callers whenever the location itself was not marked as private.\n\nThese records could contain internal fields such as header, which may include authentication headers, session cookies, or other credentials used to access monitored websites; init_script, which may contain logic used to bypass CAPTCHA, anti-bot protections, or paywalls; and browser, which discloses details about the scraping environment.\n\nAn unauthenticated remote attacker could query the affected API endpoints and obtain these values. Leaked authentication material could potentially be replayed against the monitored service, while disclosure of scraping and bypass logic could allow site operators or other attackers to identify and defeat RansomLook's collection mechanisms.\n\nThe patch introduces an explicit allowlist of fields permitted in public location records and strips all operator-side fields before returning data to unauthenticated users.\n\nThe accompanying change from \u003cstring:postname\u003e to \u003cpath:postname\u003e appears to be a functional correction allowing legitimate post titles containing / and does not, based on this patch alone, represent the security issue.","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":"Unauthenticated Disclosure of Scraping Credentials and Bypass Configuration via RansomLook API","id":"CVE-2026-78386","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":"RansomLook Missing Authorization in Web Configuration Editor Allows Application Configuration Modification","id":"CVE-2026-78387"},"packages":[],"prev":{"headline":"RansomLook Analysis PDF Generation Allows Server-Side Request Forgery and Arbitrary Local File Access","id":"CVE-2026-78385"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-24","vendors":["ransomlook"]},"summary":"Unauthenticated attackers can access sensitive scraping credentials and bypass logic via RansomLook API, potentially enabling credential replay and evasion of anti-bot protections.","url":"https://insights.sbomify.com/CVE-2026-78386/"}