{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-11968 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11968 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11968 is a medium-severity command injection vulnerability in TortoiseGit, published on 24 Jun 2026. 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-2026-11968 and fix it if it is affected.\n\nWhat it is: CVE-2026-11968 is a medium-severity command injection vulnerability in TortoiseGit, published on 24 Jun 2026. 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-2026-11968 in the wild and no public exploit code.\n\nAffected product: TortoiseGit. 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-11968/ (Markdown: https://insights.sbomify.com/CVE-2026-11968/index.md)","id":"CVE-2026-11968","markdown":"https://insights.sbomify.com/CVE-2026-11968/index.md","name":"CVE-2026-11968","record":{"aliases":["GHSA-2h5c-f427-3wjr"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Git client","requires_auth":"none","summary":"Attackers can exploit argument injection in TortoiseGitBlame via malicious filenames to achieve arbitrary file write and potential code execution.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Argument Injection in TortoiseGitBlame via Malicious Git History Filenames Leads to Arbitrary File Write in TortoiseGit","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":"Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') in TortoiseGit","id":"CVE-2026-11968","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"WP TripAdvisor Review Slider \u003c= 14.3 - Authenticated (Administrator+) SQL Injection","id":"CVE-2026-11969"},"packages":[],"prev":{"headline":"Arbitrary code execution in MobaXterm Personal Edition (Portable)","id":"CVE-2026-11967"},"products":["TortoiseGit"],"published":"2026-06-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-06-24","vendors":["TortoiseGit team"]},"summary":"Attackers can exploit argument injection in TortoiseGitBlame via malicious filenames to achieve arbitrary file write and potential code execution.","url":"https://insights.sbomify.com/CVE-2026-11968/"}