How to Fix CVE-2026-29059: Path traversal in windmill
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-29059 is a path traversal in windmill-labs windmill. The fix is to apply the vendor patch noted below.
| Severity | 6.9 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | windmill < 1.603.3 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') |
What is CVE-2026-29059?
Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Prior to version 1.603.3, an unauthenticated path traversal vulnerability exists in Windmill's get_log_file endpoint "(/api/w/{workspace}/jobs_u/get_log_file/{filename})". The filename parameter is concatenated into a file path without sanitization, allowing an attacker to read arbitrary files on the server using ../ sequences. This issue has been patched in version 1.603.3. The CVSS base score is 6.9 (Medium). The official advisory is at https://github.com/windmill-labs/windmill/security/advisories/GHSA-24fr-44f8-fqwg.
Am I affected?
Check the version of windmill you are running and compare it against the Affected row above (windmill < 1.603.3). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s windmill 2>/dev/null | grep -i ^Version
rpm -q windmill 2>/dev/null
command -v windmill >/dev/null && windmill --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*windmill*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "windmill" 2>$null
How to fix CVE-2026-29059
Upgrade windmill to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade windmill
dpkg -s windmill | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh windmill -y
# or for older releases:
sudo yum update windmill -y
rpm -q windmill
SUSE / openSUSE
sudo zypper refresh
sudo zypper update windmill
rpm -q windmill
Node.js / npm
# Update the affected package in your project
npm install windmill@latest
npm ls windmill
npm audit fix
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-29059 affecting windmill
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-29059-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detect installed version"
$pkg = Get-Package -Name "*windmill*" -ErrorAction SilentlyContinue
if ($pkg) { $pkg | Format-Table Name, Version }
else { Write-Host "Not detected via Get-Package; try winget list" }
Write-Host "[2/4] Backup configuration"
$backup = "C:\Backup\windmill-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\windmill" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "windmill" --silent --accept-source-agreements --accept-package-agreements
if ($LASTEXITCODE -ne 0) {
# Fallback: pull latest via OS update channel
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verify the patched build"
winget list --name "windmill"
Write-Host "Patch applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-29059 affecting windmill
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-29059-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
dpkg -s windmill 2>/dev/null | grep -i ^Version || echo "windmill not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q windmill || echo "windmill not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-29059-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/windmill /etc/windmill.d /etc/windmill.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y windmill
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y windmill
elif command -v yum >/dev/null; then
yum update -y windmill
elif command -v zypper >/dev/null; then
zypper --non-interactive update windmill
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s windmill 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q windmill
fi
echo "Done. Restart any service that loaded the old library."
If you can't patch immediately
Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.
Restrict exposure with nftables (Linux)
# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Block at the host firewall (Windows)
New-NetFirewallRule -DisplayName "Block-CVE-2026-29059" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-29059"
Disable the affected service (Linux)
sudo systemctl stop windmill 2>/dev/null || true
sudo systemctl disable windmill 2>/dev/null || true
If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.
How to verify the fix worked
After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.
# Linux
dpkg -s windmill 2>/dev/null | grep -i ^Version
rpm -q windmill 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true
# Windows
Get-Package -Name "*windmill*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-2503: SQL Injection in ElementCamp — SQL Injection in ElementCamp
- How to Fix CVE-2026-23975: Critical Vulnerability in Golo — Critical Vulnerability in Golo
- How to Fix CVE-2026-6452: Cross-Site Request Forgery in Bigfishgames Syndicate , Cross-Site Request Forgery in Bigfishgames Syndicate
- How to Fix CVE-2026-39461: Stack Buffer Overflow in FreeBSD , Stack Buffer Overflow in FreeBSD
- How to Fix CVE-2026-32627: CWE-295: Improper Certificate Validation in cpp-httplib , CWE-295: Improper Certificate Validation in cpp-httplib
Is CVE-2026-29059 actively exploited?
There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.
Do I need to reboot after patching CVE-2026-29059?
For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.
What is the CVSS score for CVE-2026-29059?
6.9 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N.
Where is the official advisory for CVE-2026-29059?
The vendor advisory is at https://github.com/windmill-labs/windmill/security/advisories/GHSA-24fr-44f8-fqwg. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29059.
References
- Official vendor advisory: https://github.com/windmill-labs/windmill/security/advisories/GHSA-24fr-44f8-fqwg
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29059
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/windmill-labs/windmill/releases/tag/v1.603.3
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*