How to Fix CVE-2026-3405: Path traversal in JeeSite
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-3405 is a path traversal in thinkgem JeeSite. The fix is to apply the vendor patch noted below.
| Severity | 2.3 (Low) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | JeeSite 5.15.0; JeeSite 5.15.1 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-22: Path Traversal |
What is CVE-2026-3405?
A vulnerability has been found in thinkgem JeeSite up to 5.15.1. The affected element is an unknown function of the component Connection Handler. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is described as difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way. The CVSS base score is 2.3 (Low). The official advisory is at https://vuldb.com/?id.348300.
Am I affected?
Check the version of JeeSite you are running and compare it against the Affected row above (JeeSite 5.15.0; JeeSite 5.15.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 jeesite 2>/dev/null | grep -i ^Version
rpm -q jeesite 2>/dev/null
command -v jeesite >/dev/null && jeesite --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*JeeSite*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "JeeSite" 2>$null
How to fix CVE-2026-3405
Upgrade JeeSite 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 jeesite
dpkg -s jeesite | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh jeesite -y
# or for older releases:
sudo yum update jeesite -y
rpm -q jeesite
SUSE / openSUSE
sudo zypper refresh
sudo zypper update jeesite
rpm -q jeesite
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-3405 affecting JeeSite
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-3405-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 "*JeeSite*" -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\jeesite-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\JeeSite" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "JeeSite" --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 "JeeSite"
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-3405 affecting JeeSite
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-3405-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 jeesite 2>/dev/null | grep -i ^Version || echo "jeesite not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q jeesite || echo "jeesite not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3405-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/jeesite /etc/jeesite.d /etc/jeesite.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 jeesite
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y jeesite
elif command -v yum >/dev/null; then
yum update -y jeesite
elif command -v zypper >/dev/null; then
zypper --non-interactive update jeesite
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s jeesite 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q jeesite
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-3405" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3405"
Disable the affected service (Linux)
sudo systemctl stop jeesite 2>/dev/null || true
sudo systemctl disable jeesite 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 jeesite 2>/dev/null | grep -i ^Version
rpm -q jeesite 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 "*JeeSite*" | 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-27970: Cross-site scripting in angular — Cross-site scripting in angular
- How to Fix CVE-2026-44925: Critical Vulnerability in n/a — Critical Vulnerability in n/a
- How to Fix CVE-2026-41680: CWE-400: Uncontrolled Resource Consumption in marked , CWE-400: Uncontrolled Resource Consumption in marked
- How to Fix CVE-2026-34612: Kestra: Remote Code Execution via SQL Injection in kestra , Kestra: Remote Code Execution via SQL Injection in kestra
- How to Fix CVE-2026-34455: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') , CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Is CVE-2026-3405 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-3405?
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-3405?
2.3 (Low). Vector: CVSS:4.0/AV:N/AC:H/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-3405?
The vendor advisory is at https://vuldb.com/?id.348300. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3405.
References
- Official vendor advisory: https://vuldb.com/?id.348300
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3405
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://vuldb.com/?ctiid.348300
- Additional reference: https://vuldb.com/?submit.765097
- Additional reference: https://www.yuque.com/la12138/pa2fpb/sg81mhkrat5h170c?singleDoc
*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.*