FKIE_CVE-2026-27113
Vulnerability from fkie_nvd - Published: 2026-02-20 22:16 - Updated: 2026-06-17 10:26| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "liquidprompt",
"vendor": "liquidprompt",
"versions": [
{
"status": "affected",
"version": "\u003e= cf3441250bb5d8b45f6f8b389fcdf427a99ac28a, \u003c a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
},
{
"lang": "es",
"value": "Liquid Prompt es un *prompt* adaptativo para Bash y Zsh. A partir del *commit* cf3441250bb5d8b45f6f8b389fcdf427a99ac28a y antes del *commit* a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c en la rama *master*, la inyecci\u00f3n de comandos arbitraria puede llevar a la ejecuci\u00f3n de c\u00f3digo cuando un usuario entra en un directorio de un repositorio Git que contiene un nombre de rama manipulado. La explotaci\u00f3n requiere que la opci\u00f3n de configuraci\u00f3n LP_ENABLE_GITSTATUSD est\u00e9 habilitada (habilitada por defecto), que *gitstatusd* est\u00e9 instalado e iniciado antes de que se cargue Liquid Prompt (no es el valor por defecto), y que la sustituci\u00f3n del *prompt* de la *shell* est\u00e9 activa (habilitada por defecto en Bash a trav\u00e9s de \u0027shopt -s promptvars\u0027, no habilitada por defecto en Zsh). Un nombre de rama que contenga sintaxis de *shell* como \u0027$(...)\u0027 o expresiones de *backtick* en la rama por defecto o en una rama extra\u00edda ser\u00e1 evaluado por la *shell* cuando se renderice el *prompt*. Ninguna versi\u00f3n estable est\u00e1 afectada; solo la rama *master* contiene el *commit* vulnerable. El *commit* a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c contiene una correcci\u00f3n. Como soluci\u00f3n alternativa, establezca la opci\u00f3n de configuraci\u00f3n LP_ENABLE_GITSTATUSD en 0."
}
],
"id": "CVE-2026-27113",
"lastModified": "2026-06-17T10:26:41.340",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.0,
"impactScore": 5.2,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-27113",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-23T19:36:21.539868Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-02-20T22:16:29.503",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/liquidprompt/liquidprompt/commit/a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/liquidprompt/liquidprompt/security/advisories/GHSA-q6hm-vf4f-47jf"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-78"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.