{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92791 exists.","fix":"No fix has been published for CVE-2026-92791 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92791 is a high-severity path traversal vulnerability in uber kraken, published on 16 Sep 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-92791 and fix it if it is affected.\n\nWhat it is: CVE-2026-92791 is a high-severity path traversal vulnerability in uber kraken, published on 16 Sep 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-92791 exists.\n\nAffected product: uber kraken. 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-92791/ (Markdown: https://insights.sbomify.com/CVE-2026-92791/index.md)","id":"CVE-2026-92791","markdown":"https://insights.sbomify.com/CVE-2026-92791/index.md","name":"CVE-2026-92791","record":{"aliases":["GHSA-2jmw-fcwx-7j6h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kraken image registry","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary files via path traversal in the tag parameter of the Uber Kraken image registry.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","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-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Uber Kraken through 0.1.29 fails to validate the tag parameter in the /tags/{tag} endpoint, allowing unauthenticated attackers to traverse outside the configured storage root. Attackers can use percent-encoded parent-directory segments in the tag parameter to read arbitrary files accessible to the testfs backend process.","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":"Uber Kraken through 0.1.29 Path Traversal via tag parameter","id":"CVE-2026-92791","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"OpenNHP through 1.0.2 Authentication Bypass via Fallback Verifier","id":"CVE-2026-92792"},"packages":[],"prev":{"headline":"Higress before 2.2.4 Rate Limit Bypass via Malformed Cookie Header","id":"CVE-2026-92790"},"products":["kraken"],"published":"2026-09-16","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["uber"]},"summary":"Unauthenticated attackers can read arbitrary files via path traversal in the tag parameter of the Uber Kraken image registry.","url":"https://insights.sbomify.com/CVE-2026-92791/"}