{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-27113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27113 is a medium-severity command injection vulnerability in liquidprompt, published on 20 Feb 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-27113 and fix it if it is affected.\n\nWhat it is: CVE-2026-27113 is a medium-severity command injection vulnerability in liquidprompt, published on 20 Feb 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-27113 in the wild and no public exploit code.\n\nAffected product: liquidprompt. 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-27113/ (Markdown: https://insights.sbomify.com/CVE-2026-27113/index.md)","id":"CVE-2026-27113","markdown":"https://insights.sbomify.com/CVE-2026-27113/index.md","name":"CVE-2026-27113","record":{"aliases":["GHSA-q6hm-vf4f-47jf","UBUNTU-CVE-2026-27113"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Shell prompt tool","requires_auth":"none","summary":"Attackers can execute arbitrary code via crafted Git branch names when Liquid Prompt renders the shell prompt with gitstatusd enabled.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Liquid Prompt is an adaptive prompt for Bash and Zsh. Starting in commit cf3441250bb5d8b45f6f8b389fcdf427a99ac28a and prior to commit a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c on the master branch, arbitrary command injection can lead to code execution when a user enters a directory in a Git repository containing a crafted branch name. Exploitation requires the LP_ENABLE_GITSTATUSD config option to be enabled (enabled by default), gitstatusd to be installed and started before Liquid Prompt is loaded (not the default), and shell prompt substitution to be active (enabled by default in Bash via \"shopt -s promptvars\", not enabled by default in Zsh). A branch name containing shell syntax such as \"$(...)\" or backtick expressions in the default branch or a checked-out branch will be evaluated by the shell when the prompt is rendered. No stable release is affected; only the master branch contains the vulnerable commit. Commit a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c contains a fix. As a workaround, set the LP_ENABLE_GITSTATUSD config option to 0.","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":"Liquid Prompt arbitrary command injection via crafted Git branch names in gitstatusd backend","id":"CVE-2026-27113","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":"NanaZip has ROMFS Archive Infinite Loop","id":"CVE-2026-27114"},"packages":[],"prev":{"headline":"Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints","id":"CVE-2026-27112"},"products":["liquidprompt"],"published":"2026-02-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-02-23","vendors":["liquidprompt"]},"summary":"Attackers can execute arbitrary code via crafted Git branch names when Liquid Prompt renders the shell prompt with gitstatusd enabled.","url":"https://insights.sbomify.com/CVE-2026-27113/"}