How to Fix CVE-2026-34430: ByteDance DeerFlow LocalSandboxProvider Host Bash Escape in DeerFlow
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-25396: Critical Vulnerability in Commerce Coinbase For WooCommerce — Critical Vulnerability in Commerce Coinbase For WooCommerce
- How to Fix CVE-2026-25047: Critical Vulnerability in deepHas — Critical Vulnerability in deepHas
- How to Fix CVE-2026-24481: Out-of-bounds read in ImageMagick , Out-of-bounds read in ImageMagick
- How to Fix CVE-2026-34212: Cross-site scripting in docmost , Cross-site scripting in docmost
- How to Fix CVE-2026-44076: Command Injection in Netatalk , Command Injection in Netatalk
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 8.6, High |
|---|---|
| Actively exploited? | No |
| Affected | Bytedance Inc. DeerFlow (0 < 92c7a20cb74addc3038d2131da78f2e239ef542e) |
| Fixed in | 92c7a20cb74addc3038d2131da78f2e239ef542e |
| Type (CWE) | CWE-184: Incomplete List of Disallowed Inputs |
CVE-2026-34430 is a bytedance deerflow localsandboxprovider host bash escape in Bytedance Inc. DeerFlow. The fix is to upgrade to 92c7a20cb74addc3038d2131da78f2e239ef542e and apply the runnable commands below.
What is CVE-2026-34430?
ByteDance DeerFlow versions prior to commit 92c7a20 contain a sandbox escape vulnerability in bash tool handling that allows attackers to execute arbitrary commands on the host system by bypassing regex-based validation using shell features such as directory changes and relative paths. Attackers can exploit the incomplete shell semantics modeling to read and modify files outside the sandbox boundary and achieve arbitrary command execution through subprocess invocation with shell interpretation enabled.
In practical terms, a successful attacker gets a security bypass on the affected component. 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 Bytedance Inc. DeerFlow 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 deerflow # Debian/Ubuntu
rpm -qa | grep -i deerflow # RHEL/CentOS/Rocky
How to fix CVE-2026-34430
The primary fix is to upgrade to the patched build listed in the Fixed in row above (92c7a20cb74addc3038d2131da78f2e239ef542e). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
sudo apt-get update
sudo apt-get install --only-upgrade deerflow
# Confirm the installed version meets or exceeds 92c7a20cb74addc3038d2131da78f2e239ef542e
dpkg -s deerflow | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security deerflow -y
rpm -q deerflow
Windows (PowerShell, admin)
winget upgrade --id 'BytedanceInc.DeerFlow' --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\DeerFlow-92c7a20cb74addc3038d2131da78f2e239ef542e.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows): detect, back up, upgrade, verify, log
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\DeerFlow-Patch-CVE-2026-34430.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-34430 remediation for Bytedance Inc. DeerFlow"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*DeerFlow*' } |
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]'92c7a20cb74addc3038d2131da78f2e239ef542e') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\DeerFlow-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Bytedance Inc.\DeerFlow"
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\DeerFlow-92c7a20cb74addc3038d2131da78f2e239ef542e.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 '*DeerFlow*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'92c7a20cb74addc3038d2131da78f2e239ef542e') {
Write-Log "SUCCESS: now at $verify (>= 92c7a20cb74addc3038d2131da78f2e239ef542e)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux): detect, back up, upgrade, verify, log
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/deerflow-patch-cve-2026-34430.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-34430 remediation for Bytedance Inc. DeerFlow"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s deerflow >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' deerflow)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q deerflow >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' deerflow)
PKG_MGR=dnf
else
log "deerflow not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: deerflow=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/deerflow-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/deerflow /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 deerflow
else
sudo dnf upgrade --security -y deerflow
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' deerflow)
else
NEW=$(rpm -q --queryformat '%{VERSION}' deerflow)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against 92c7a20cb74addc3038d2131da78f2e239ef542e 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.
No official vendor workaround is published for this CVE; patching is the documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.
Restrict the affected service to trusted networks (Linux):
# Vendor advisory: https://github.com/bytedance/deer-flow/pull/1547
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP
Windows Firewall equivalent:
# Vendor advisory: https://github.com/bytedance/deer-flow/pull/1547
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>
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 "deerflow" # Debian/Ubuntu
rpm -qa | grep -i "deerflow" # RHEL/CentOS/Rocky
Expected output: the package version should meet or exceed 92c7a20cb74addc3038d2131da78f2e239ef542e.
Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-34430 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-34430 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-34430?
CVSS rates it 8.6 (High). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take DeerFlow 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-34430 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://github.com/bytedance/deer-flow/pull/1547
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-34430
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/bytedance/deer-flow/commit/92c7a20cb74addc3038d2131da78f2e239ef542e
- Additional reference: https://www.vulncheck.com/advisories/bytedance-deerflow-localsandboxprovider-host-bash-escape
*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.*