How to Fix CVE-2026-25648: Cross-site scripting in traccar
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-25648 is a cross-site scripting in traccar traccar. The fix is to apply the vendor patch noted below.
| Severity | 8.7 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | traccar >= 6.11.1 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
What is CVE-2026-25648?
Versions of the Traccar open-source GPS tracking system starting with 6.11.1 contain an issue in which authenticated users can execute arbitrary JavaScript in the context of other users' browsers by uploading malicious SVG files as device images. The application accepts SVG file uploads without sanitization and serves them with the image/svg+xml Content-Type, allowing embedded JavaScript to execute when victims view the image. As of time of publication, it is unclear whether a fix is available. The CVSS base score is 8.7 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/traccar/traccar/security/advisories/GHSA-mc2g-mjqh-8x78.
Am I affected?
Check the version of traccar you are running and compare it against the Affected row above (traccar >= 6.11.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 traccar 2>/dev/null | grep -i ^Version
rpm -q traccar 2>/dev/null
command -v traccar >/dev/null && traccar --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*traccar*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "traccar" 2>$null
How to fix CVE-2026-25648
Upgrade traccar 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 traccar
dpkg -s traccar | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh traccar -y
# or for older releases:
sudo yum update traccar -y
rpm -q traccar
SUSE / openSUSE
sudo zypper refresh
sudo zypper update traccar
rpm -q traccar
Node.js / npm
# Update the affected package in your project
npm install traccar@latest
npm ls traccar
npm audit fix
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-25648 affecting traccar
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-25648-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 "*traccar*" -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\traccar-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\traccar" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "traccar" --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 "traccar"
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-25648 affecting traccar
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-25648-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 traccar 2>/dev/null | grep -i ^Version || echo "traccar not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q traccar || echo "traccar not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-25648-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/traccar /etc/traccar.d /etc/traccar.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 traccar
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y traccar
elif command -v yum >/dev/null; then
yum update -y traccar
elif command -v zypper >/dev/null; then
zypper --non-interactive update traccar
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s traccar 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q traccar
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-25648" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-25648"
Disable the affected service (Linux)
sudo systemctl stop traccar 2>/dev/null || true
sudo systemctl disable traccar 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 traccar 2>/dev/null | grep -i ^Version
rpm -q traccar 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 "*traccar*" | 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-1071: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') — CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- How to Fix CVE-2026-3791: SourceCodester Sales and Inventory System Search dashboard.php sql injection — SourceCodester Sales and Inventory System Search dashboard.php sql injection
- How to Fix CVE-2026-30969: CWE-639: Authorization Bypass Through User-Controlled Key in coral-server , CWE-639: Authorization Bypass Through User-Controlled Key in coral-server
- How to Fix CVE-2026-31840: Parse Server has a SQL injection via dot-notation field name in PostgreSQL , Parse Server has a SQL injection via dot-notation field name in PostgreSQL
- How to Fix CVE-2026-8137: Buffer Overflow in X5000R , Buffer Overflow in X5000R
Is CVE-2026-25648 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-25648?
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-25648?
8.7 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N.
Where is the official advisory for CVE-2026-25648?
The vendor advisory is at https://github.com/traccar/traccar/security/advisories/GHSA-mc2g-mjqh-8x78. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-25648.
References
- Official vendor advisory: https://github.com/traccar/traccar/security/advisories/GHSA-mc2g-mjqh-8x78
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25648
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*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.*