{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53584 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53584 is a medium-severity path traversal vulnerability in libgit2, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-53584 and fix it if it is affected.\n\nWhat it is: CVE-2026-53584 is a medium-severity path traversal vulnerability in libgit2, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-53584 in the wild and no public exploit code.\n\nAffected product: libgit2. 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-53584/ (Markdown: https://insights.sbomify.com/CVE-2026-53584/index.md)","id":"CVE-2026-53584","markdown":"https://insights.sbomify.com/CVE-2026-53584/index.md","name":"CVE-2026-53584","record":{"aliases":["AZL-96974","BELL-CVE-2026-53584","DEBIAN-CVE-2026-53584","ECHO-922d-f336-ad57","GHSA-cw77-j82w-mchm","JLSEC-2026-1370","MINI-59gg-pgrc-5xhh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Git core library","requires_auth":"none","summary":"Attackers can create directories outside the repository working tree via crafted submodule paths in libgit2, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid API, allowing to build Git functionality into your application. Prior to 1.8.6 and 1.9.5, libgit2 does not reject traversal components in a submodule path loaded from .gitmodules. The affected src/libgit2/submodule.c paths include git_submodule_lookup and git_submodule_add_setup. A crafted repository can specify a path such as ../escape-target, and applications that initialize the submodule can create directories outside the repository working tree. This issue is fixed in versions 1.8.6 and 1.9.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"libgit2: Submodule path traversal","id":"CVE-2026-53584","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":"libgit2: Unbounded Memory Allocation via Delta Object Result-Size Header","id":"CVE-2026-53585"},"packages":[],"prev":{"headline":"libgit2: Inverted IP SubjectAltName Comparison in OpenSSL Backend","id":"CVE-2026-53583"},"products":["libgit2"],"published":"2026-08-20","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-20","vendors":["libgit2"]},"summary":"Attackers can create directories outside the repository working tree via crafted submodule paths in libgit2, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2026-53584/"}