{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27613 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-27613 is a low-severity path traversal vulnerability in j6t gitk, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-27613 and fix it if it is affected.\n\nWhat it is: CVE-2025-27613 is a low-severity path traversal vulnerability in j6t gitk, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-27613 in the wild and no public exploit code.\n\nAffected product: j6t gitk. 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-2025-27613/ (Markdown: https://insights.sbomify.com/CVE-2025-27613/index.md)","id":"CVE-2025-27613","markdown":"https://insights.sbomify.com/CVE-2025-27613/index.md","name":"CVE-2025-27613","record":{"aliases":["ALPINE-CVE-2025-27613","AZL-65073","AZL-65076","BELL-CVE-2025-27613","CLSA-2025-1754346021","CLSA-2025-1754381382","CLSA-2025-1754940262","CLSA-2025-1754940505","CLSA-2025-1754941109","CLSA-2025-1756929133","DEBIAN-CVE-2025-27613","ECHO-b1d0-a192-7995","GHSA-f3cw-xrj3-wr2v","ROOT-OS-DEBIAN-12-CVE-2025-27613"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Git history browser","requires_auth":"none","summary":"Gitk allows attackers to create or truncate files in the user's home directory via a malicious repository clone, requiring specific preference settings or UI interactions.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.","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":"Gitk can create and truncate files in the user's home directory","id":"CVE-2025-27613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Gitk allows arbitrary command execution","id":"CVE-2025-27614"},"packages":[],"prev":{"headline":"Libcontainer is affected by capabilities elevation","id":"CVE-2025-27612"},"products":["gitk"],"published":"2025-07-10","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":"2025-11-04","vendors":["j6t"]},"summary":"Gitk allows attackers to create or truncate files in the user's home directory via a malicious repository clone, requiring specific preference settings or UI interactions.","url":"https://insights.sbomify.com/CVE-2025-27613/"}