How to Fix CVE-2026-27884: Path traversal in NetExec
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-27884 is a path traversal in Pennyw0rth NetExec. The fix is to apply the vendor patch noted below.
| Severity | 5.3 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | NetExec < 1.5.1 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') |
What is CVE-2026-27884?
NetExec is a network execution tool. Prior to version 1.5.1, the module spider_plus improperly creates the output file and folder path when saving files from SMB shares. It does not take into account that it is possible for Linux SMB shares to have path traversal characters such as ../ in them. An attacker can craft a filename in an SMB share that includes these characters, which when spider_plus crawls and downloads, can write or overwrite arbitrary files. The issue is patched in v1.5.1. As a workaround, do not run spider_plus with DOWNLOAD=true against targets. The CVSS base score is 5.3 (Medium). The official advisory is at https://github.com/Pennyw0rth/NetExec/security/advisories/GHSA-fccr-6qm2-7h27.
Am I affected?
Check the version of NetExec you are running and compare it against the Affected row above (NetExec < 1.5.1). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s netexec 2>/dev/null | grep -i ^Version
rpm -q netexec 2>/dev/null
command -v netexec >/dev/null && netexec --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*NetExec*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "NetExec" 2>$null
How to fix CVE-2026-27884
Upgrade NetExec 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 netexec
dpkg -s netexec | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh netexec -y
# or for older releases:
sudo yum update netexec -y
rpm -q netexec
SUSE / openSUSE
sudo zypper refresh
sudo zypper update netexec
rpm -q netexec
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-27884 affecting NetExec
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-27884-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 "*NetExec*" -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\netexec-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\NetExec" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "NetExec" --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 "NetExec"
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-27884 affecting NetExec
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-27884-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 netexec 2>/dev/null | grep -i ^Version || echo "netexec not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q netexec || echo "netexec not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27884-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/netexec /etc/netexec.d /etc/netexec.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 netexec
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y netexec
elif command -v yum >/dev/null; then
yum update -y netexec
elif command -v zypper >/dev/null; then
zypper --non-interactive update netexec
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s netexec 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q netexec
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-27884" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27884"
Disable the affected service (Linux)
sudo systemctl stop netexec 2>/dev/null || true
sudo systemctl disable netexec 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 netexec 2>/dev/null | grep -i ^Version
rpm -q netexec 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 "*NetExec*" | 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-24806: Code Injection RCE in quick-media — Code Injection RCE in quick-media
- How to Fix CVE-2026-4105: Improper Access Control in Red Hat Hardened Images — Improper Access Control in Red Hat Hardened Images
- How to Fix CVE-2026-3352: Code injection in Easy PHP Settings , Code injection in Easy PHP Settings
- How to Fix CVE-2026-1526: CWE-409 Improper handling of highly compressed data (data amplification) , CWE-409 Improper handling of highly compressed data (data amplification)
- How to Fix CVE-2026-3815: UTT HiPER 810G formApMail strcpy buffer overflow in HiPER 810G , UTT HiPER 810G formApMail strcpy buffer overflow in HiPER 810G
Is CVE-2026-27884 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-27884?
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-27884?
5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N.
Where is the official advisory for CVE-2026-27884?
The vendor advisory is at https://github.com/Pennyw0rth/NetExec/security/advisories/GHSA-fccr-6qm2-7h27. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27884.
References
- Official vendor advisory: https://github.com/Pennyw0rth/NetExec/security/advisories/GHSA-fccr-6qm2-7h27
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27884
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/Pennyw0rth/NetExec/issues/1120
- Additional reference: https://github.com/Pennyw0rth/NetExec/pull/1121
- Additional reference: https://github.com/Pennyw0rth/NetExec/commit/7d027f2774d0520b322d60f9c99b9ab3edb4035e
*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.*