How to Fix CVE-2026-5741: suvarchal docker-mcp-server HTTP index.ts pull_image os command injection
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-27169: Critical Vulnerability in OpenSift — Critical Vulnerability in OpenSift
- How to Fix CVE-2026-27975: Improper access control in ajenti — Improper access control in ajenti
- How to Fix CVE-2026-24899: Authentication Bypass in fleet , Authentication Bypass in fleet
- How to Fix CVE-2026-7267: SQL Injection in Pizzafy Ecommerce System , SQL Injection in Pizzafy Ecommerce System
- How to Fix CVE-2026-2936: Visitor Traffic Real Time Statistics <= 8.4 - Unauthenticated Stored Cross-Site Scripting , Visitor Traffic Real Time Statistics <= 8.4 - Unauthenticated Stored Cross-Site Scripting
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 6.9, Medium |
|---|---|
| Actively exploited? | No |
| Affected | Suvarchal docker-mcp-server (0.1.0) |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-78: OS Command Injection |
CVE-2026-5741 is a suvarchal docker-mcp-server http index.ts pull_image os command injection in Suvarchal docker-mcp-server. The fix is to upgrade to see vendor advisory and apply the runnable commands below.
What is CVE-2026-5741?
A weakness has been identified in suvarchal docker-mcp-server up to 0.1.0. The impacted element is the function stop_container/remove_container/pull_image of the file src/index.ts of the component HTTP Interface. This manipulation causes os command injection.
In practical terms, a successful attacker gets command injection on the host operating system. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.
Am I affected?
You are affected if you run Suvarchal docker-mcp-server at a version listed in the Affected row above. Probe your installed build with the commands below.
# Confirm the installed version via your package manager
dpkg -l | grep -i docker-mcp-server # Debian/Ubuntu
rpm -qa | grep -i docker-mcp-server # RHEL/CentOS/Rocky
How to fix CVE-2026-5741
The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
# Vendor advisory: https://vuldb.com/vuln/355748
sudo apt-get update
sudo apt-get install --only-upgrade docker-mcp-server
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s docker-mcp-server | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security docker-mcp-server -y
rpm -q docker-mcp-server
Windows (PowerShell, admin)
# Vendor advisory: https://vuldb.com/vuln/355748
winget upgrade --id 'Suvarchal.dockermcpserver' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\dockermcpserver-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows): detect, back up, upgrade, verify, log
# Vendor advisory: https://vuldb.com/vuln/355748
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\dockermcpserver-Patch-CVE-2026-5741.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-5741 remediation for Suvarchal docker-mcp-server"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*docker-mcp-server*' } |
Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"
if (-not $installed) {
Write-Log "Product not installed on this host; nothing to do."
return
}
if ([version]$installed -ge [version]'<patched-version>') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\dockermcpserver-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Suvarchal\docker-mcp-server"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"
# 3. Apply the patched installer
$installer = "$env:TEMP\dockermcpserver-<patched-version>.msi"
if (-not (Test-Path $installer)) {
throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"
# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*docker-mcp-server*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux): detect, back up, upgrade, verify, log
# Vendor advisory: https://vuldb.com/vuln/355748
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/docker-mcp-server-patch-cve-2026-5741.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-5741 remediation for Suvarchal docker-mcp-server"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s docker-mcp-server >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' docker-mcp-server)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q docker-mcp-server >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' docker-mcp-server)
PKG_MGR=dnf
else
log "docker-mcp-server not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: docker-mcp-server=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/docker-mcp-server-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/docker-mcp-server /etc/${pkg%%-*} ; do
[ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done
# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
sudo apt-get update -y
sudo apt-get install --only-upgrade -y docker-mcp-server
else
sudo dnf upgrade --security -y docker-mcp-server
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' docker-mcp-server)
else
NEW=$(rpm -q --queryformat '%{VERSION}' docker-mcp-server)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against <patched-version> and restart the affected service if needed."
If you cannot patch immediately
These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.
Rate-limit and log the affected endpoint at the reverse proxy
limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
limit_req zone=admin burst=5 nodelay;
access_log /var/log/nginx/admin-access.log combined;
proxy_pass http://backend;
}
How to verify the fix worked
Run the version probe again and confirm the running build matches the Fixed in row above.
dpkg -l | grep -i "docker-mcp-server" # Debian/Ubuntu
rpm -qa | grep -i "docker-mcp-server" # RHEL/CentOS/Rocky
Expected output: the package version should meet or exceed the patched build.
Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-5741 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.
Frequently asked questions
Is CVE-2026-5741 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-5741?
CVSS rates it 6.9 (Medium). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take docker-mcp-server offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-5741 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://vuldb.com/vuln/355748
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-5741
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://vuldb.com/vuln/355748/cti
- Additional reference: https://vuldb.com/submit/786948
- Additional reference: https://github.com/suvarchal/docker-mcp/issues/3
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*