How to Fix CVE-2026-21410: Sql injection in MasterSCADA BUK-TS
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-21410 is a SQL injection in InSAT MasterSCADA BUK-TS. The fix is to apply the vendor patch noted below.
| Severity | 9.8 (Critical) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | MasterSCADA BUK-TS All versions |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-89 |
What is CVE-2026-21410?
InSAT MasterSCADA BUK-TS is susceptible to SQL Injection through its main web interface. Malicious users that use the vulnerable endpoint are potentially able to cause remote code execution. The CVSS base score is 9.8 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://www.cisa.gov/news-events/ics-advisories/icsa-26-055-01.
Am I affected?
Check the version of MasterSCADA BUK-TS you are running and compare it against the Affected row above (MasterSCADA BUK-TS All versions). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s masterscada-buk-ts 2>/dev/null | grep -i ^Version
rpm -q masterscada-buk-ts 2>/dev/null
command -v masterscada-buk-ts >/dev/null && masterscada-buk-ts --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*MasterSCADA BUK-TS*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "MasterSCADA BUK-TS" 2>$null
How to fix CVE-2026-21410
Upgrade MasterSCADA BUK-TS 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 masterscada-buk-ts
dpkg -s masterscada-buk-ts | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh masterscada-buk-ts -y
# or for older releases:
sudo yum update masterscada-buk-ts -y
rpm -q masterscada-buk-ts
SUSE / openSUSE
sudo zypper refresh
sudo zypper update masterscada-buk-ts
rpm -q masterscada-buk-ts
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-21410 affecting MasterSCADA BUK-TS
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-21410-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 "*MasterSCADA BUK-TS*" -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\masterscada-buk-ts-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\MasterSCADA BUK-TS" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "MasterSCADA BUK-TS" --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 "MasterSCADA BUK-TS"
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-21410 affecting MasterSCADA BUK-TS
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-21410-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 masterscada-buk-ts 2>/dev/null | grep -i ^Version || echo "masterscada-buk-ts not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q masterscada-buk-ts || echo "masterscada-buk-ts not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-21410-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/masterscada-buk-ts /etc/masterscada-buk-ts.d /etc/masterscada-buk-ts.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 masterscada-buk-ts
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y masterscada-buk-ts
elif command -v yum >/dev/null; then
yum update -y masterscada-buk-ts
elif command -v zypper >/dev/null; then
zypper --non-interactive update masterscada-buk-ts
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s masterscada-buk-ts 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q masterscada-buk-ts
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-21410" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-21410"
Disable the affected service (Linux)
sudo systemctl stop masterscada-buk-ts 2>/dev/null || true
sudo systemctl disable masterscada-buk-ts 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 masterscada-buk-ts 2>/dev/null | grep -i ^Version
rpm -q masterscada-buk-ts 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 "*MasterSCADA BUK-TS*" | 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-41423: Server-Side Request Forgery (SSRF) in angular — Server-Side Request Forgery (SSRF) in angular
- How to Fix CVE-2026-7788: Path Traversal in MCP-Docusaurus — Path Traversal in MCP-Docusaurus
- How to Fix CVE-2026-25395: Critical Vulnerability in Business Roy , Critical Vulnerability in Business Roy
- How to Fix CVE-2026-5974: MetaGPT (Bundle Sibling) , MetaGPT (Bundle Sibling)
- How to Fix CVE-2026-0495: Critical Vulnerability in SAP Fiori App (Intercompany Balance Reconciliation) , Critical Vulnerability in SAP Fiori App (Intercompany Balance Reconciliation)
Is CVE-2026-21410 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-21410?
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-21410?
9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Where is the official advisory for CVE-2026-21410?
The vendor advisory is at https://www.cisa.gov/news-events/ics-advisories/icsa-26-055-01. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-21410.
References
- Official vendor advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-055-01
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21410
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-055-01.json
*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.*