● Medium · CVSS 6.3

How to Fix CVE-2026-27113: Command Injection in liquidprompt

Q: Is CVE-2026-27113 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-27113?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: Do I need to assume compromise if my liquidprompt was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-39395: Cosign's verify-blob-attestation reports false positive when payload parsing fails — Cosign's verify-blob-attestation reports false positive when payload parsing fails
How to Fix CVE-2026-43583: Missing Authorization in OpenClaw — Missing Authorization in OpenClaw
How to Fix CVE-2026-3172: Integer underflow in pgvector , Integer underflow in pgvector
How to Fix CVE-2026-2234: Authentication Bypass in C&Cm@il package olln-base , Authentication Bypass in C&Cm@il package olln-base
How to Fix CVE-2026-43002: Incorrect Behavior Order in Horizon , Incorrect Behavior Order in Horizon

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 6.3 - Medium
Actively exploited?	Not currently listed in CISA KEV
Affected	>= cf3441250bb5d8b45f6f8b389fcdf427a99ac28a, < a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c
Fixed in	See vendor advisory
Type (CWE)	CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

What is CVE-2026-27113?

CVE-2026-27113 is an OS command injection bug in liquidprompt. The product builds a shell command from untrusted input without escaping, so injected metacharacters run as the service account, often root or SYSTEM. Vendor 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.

Why this CVE matters

Command injection in a network appliance or management console gives the attacker the same privileges as the service account, which is usually root or SYSTEM. From there, persistence, lateral movement, and credential theft follow with off-the-shelf tooling.

For deployments of liquidprompt that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

liquidprompt: >= cf3441250bb5d8b45f6f8b389fcdf427a99ac28a, < a4f6b8d8c90b3eaa33d13dfd1093062ab9c4b30c

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open liquidprompt's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-27113

Read the vendor advisory in full: https://github.com/liquidprompt/liquidprompt/security/advisories/GHSA-q6hm-vf4f-47jf
Upgrade liquidprompt to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

npm / Yarn / pnpm


# Vendor advisory: https://github.com/liquidprompt/liquidprompt/security/advisories/GHSA-q6hm-vf4f-47jf
# Update to the patched release named in the advisory
npm install liquidprompt@latest
# or pin to the exact fixed version from the vendor advisory
npm install liquidprompt@<patched-version>
npm ls liquidprompt

PyPI (pip / Poetry)


# Vendor advisory: https://github.com/liquidprompt/liquidprompt/security/advisories/GHSA-q6hm-vf4f-47jf
pip install --upgrade liquidprompt
pip show liquidprompt | grep -i version
# Poetry:
poetry add liquidprompt@^<patched-version>

Docker / container


# Vendor advisory: https://github.com/liquidprompt/liquidprompt/security/advisories/GHSA-q6hm-vf4f-47jf
docker pull <your-registry>/liquidprompt:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/liquidprompt:<patched-tag>

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-27113 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-27113-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'liquidprompt' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-27113-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'liquidprompt' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-27113 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-27113-fix.log; }

log "Detect: current bash version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' bash 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' bash 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-27113-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/bash ] && cp -a /etc/bash "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade bash
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y bash
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y bash
fi

log "Verify: re-reading bash version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' bash)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' bash)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: bash upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

Restrict access to the management or affected endpoint at the network layer. If the vendor lists a configuration toggle that disables the vulnerable feature, use it until you can patch.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-27113.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in liquidprompt, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-27113 being exploited in the wild?