{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-78369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-78369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-78369 is a high-severity missing authorization 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-78369 and fix it if it is affected.\n\nWhat it is: CVE-2026-78369 is a high-severity missing authorization 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-78369 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-78369/ (Markdown: https://insights.sbomify.com/CVE-2026-78369/index.md)","id":"CVE-2026-78369","markdown":"https://insights.sbomify.com/CVE-2026-78369/index.md","name":"CVE-2026-78369","record":{"aliases":["GHSA-hqq4-44wm-8ch5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RansomLook web app","requires_auth":"none","summary":"Unauthenticated attackers can create crypto groups in RansomLook due to missing authentication on an admin endpoint, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"RansomLook contains a missing authentication vulnerability in the /admin/crypto/group/new endpoint. While the endpoint provides an administrative function for creating new crypto group entries, it was not protected by the application's authentication mechanism.\n\nAn unauthenticated remote attacker able to access the RansomLook web interface could therefore submit requests to this endpoint and create crypto group entries without possessing a valid authenticated session or administrative credentials.\n\nSuccessful exploitation allows an attacker to make unauthorized modifications to data that should only be manageable by authenticated administrators. Depending on how crypto group information is subsequently consumed by RansomLook, malicious or fraudulent entries could also affect the integrity of information presented or processed by the application.\n\nThe vulnerability is addressed by applying the flask_login.login_required decorator to the /admin/crypto/group/new route, ensuring that only authenticated users can access the functionality.","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":"Missing Authentication Allows Unauthorized Creation of Crypto Groups in RansomLook","id":"CVE-2026-78369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"RansomLook Unauthenticated Database Export Exposes Private Data","id":"CVE-2026-78370"},"packages":[],"prev":{"headline":"Rpm: rpmbuild gettarspec() crafted tar member name → macro injection","id":"CVE-2026-78367"},"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 create crypto groups in RansomLook due to missing authentication on an admin endpoint, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2026-78369/"}