How to Fix CVE-2026-3188: Path traversal in sz-boot-parent

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-3188 is a path traversal in feiyuchuixue sz-boot-parent. The fix is to upgrade to sz-boot-parent 1.3.3-beta.

What is CVE-2026-3188?

A security flaw has been discovered in feiyuchuixue sz-boot-parent up to 1.3.2-beta. This affects an unknown part of the file /api/admin/common/download/templates of the component API. Performing a manipulation of the argument templateName results in path traversal. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. Upgrading to version 1.3.3-beta is able to mitigate this issue. The patch is named aefaabfd7527188bfba3c8c9eee17c316d094802. It is recommended to upgrade the affected component. The project was informed beforehand and acted very professional: "We have implemented path validity checks on parameters for the template download interface (...)" The CVSS base score is 5.3 (Medium). The official advisory is at https://vuldb.com/?id.347746.

Am I affected?

Check the version of sz-boot-parent you are running and compare it against the Affected row above (sz-boot-parent 1.3.2-beta). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

# Linux package check
dpkg -s sz-boot-parent 2>/dev/null | grep -i ^Version
rpm -q sz-boot-parent 2>/dev/null
command -v sz-boot-parent >/dev/null && sz-boot-parent --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*sz-boot-parent*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "sz-boot-parent" 2>$null

How to fix CVE-2026-3188

Upgrade sz-boot-parent to a patched build: sz-boot-parent 1.3.3-beta. 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 sz-boot-parent
dpkg -s sz-boot-parent | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh sz-boot-parent -y
# or for older releases:
sudo yum update sz-boot-parent -y
rpm -q sz-boot-parent

SUSE / openSUSE

sudo zypper refresh
sudo zypper update sz-boot-parent
rpm -q sz-boot-parent

Node.js / npm

# Update the affected package in your project
npm install sz-boot-parent@latest
npm ls sz-boot-parent
npm audit fix

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-3188 affecting sz-boot-parent
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-3188-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 "*sz-boot-parent*" -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\sz-boot-parent-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\sz-boot-parent" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to sz-boot-parent 1.3.3-beta"
    winget upgrade --name "sz-boot-parent" --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 "sz-boot-parent"
    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-3188 affecting sz-boot-parent
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-3188-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 sz-boot-parent 2>/dev/null | grep -i ^Version || echo "sz-boot-parent not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q sz-boot-parent || echo "sz-boot-parent not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3188-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/sz-boot-parent /etc/sz-boot-parent.d /etc/sz-boot-parent.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: sz-boot-parent 1.3.3-beta)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y sz-boot-parent
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y sz-boot-parent
elif command -v yum >/dev/null; then
    yum update -y sz-boot-parent
elif command -v zypper >/dev/null; then
    zypper --non-interactive update sz-boot-parent
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s sz-boot-parent 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q sz-boot-parent
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-3188" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3188"

Disable the affected service (Linux)

sudo systemctl stop sz-boot-parent 2>/dev/null || true
sudo systemctl disable sz-boot-parent 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 sz-boot-parent 2>/dev/null | grep -i ^Version
rpm -q sz-boot-parent 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 "*sz-boot-parent*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above sz-boot-parent 1.3.3-beta. 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-33804: Cwe-436: interpretation conflict in @fastify/middie — Cwe-436: interpretation conflict in @fastify/middie
• How to Fix CVE-2026-2131: Command Injection in HarmonyOS-mcp-server — Command Injection in HarmonyOS-mcp-server
• How to Fix CVE-2026-1521: Critical Vulnerability in Open5GS , Critical Vulnerability in Open5GS
• How to Fix CVE-2026-32981: Ray Dashboard <= 2.8.0 Path Traversal Leading to Local File Disclosure , Ray Dashboard <= 2.8.0 Path Traversal Leading to Local File Disclosure
• How to Fix CVE-2026-44002: Critical Vulnerability in vm2 , Critical Vulnerability in vm2

Is CVE-2026-3188 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-3188?

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-3188?

5.3 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P.

Where is the official advisory for CVE-2026-3188?

The vendor advisory is at https://vuldb.com/?id.347746. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3188.

References

• Official vendor advisory: https://vuldb.com/?id.347746
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3188
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://vuldb.com/?ctiid.347746
• Additional reference: https://vuldb.com/?submit.754041
• Additional reference: https://github.com/yuccun/CVE/blob/main/sz-boot-parent-Path_Traversal_to_Arbitrary_Resource_File_Read.md

*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.*