How to Fix CVE-2026-20801: Cwe-319 cleartext transmission of sensitive information in NxWitness VMS and Hanwha VMS Integrations
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-20801 is a cwe-319 cleartext transmission of sensitive information in Gallagher NxWitness VMS and Hanwha VMS Integrations. The fix is to apply the vendor patch noted below.
| Severity | 5.6 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | NxWitness VMS and Hanwha VMS Integrations 0 to <9.10.017; NxWitness VMS and Hanwha VMS Integrations 0 to <9.10.025 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-319 Cleartext Transmission of Sensitive Information |
What is CVE-2026-20801?
Cleartext Transmission of Sensitive Information (CWE-319) in a component used in the Gallagher Hanwha VMS and Gallagher NxWitness VMS integrations allows unprivileged users with local network access to view live video streams.
This issue affects all versions of Gallagher NxWitness VMS integration prior to 9.10.017 and Gallagher Hanwha VMS integration prior to 9.10.025. The CVSS base score is 5.6 (Medium). The official advisory is at https://security.gallagher.com/en-NZ/Security-Advisories/CVE-2026-20801.
Am I affected?
Check the version of NxWitness VMS and Hanwha VMS Integrations you are running and compare it against the Affected row above (NxWitness VMS and Hanwha VMS Integrations 0 to <9.10.017; NxWitness VMS and Hanwha VMS Integrations 0 to <9.10.025). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null | grep -i ^Version
rpm -q nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null
command -v nxwitness-vms-and-hanwha-vms-integrations >/dev/null && nxwitness-vms-and-hanwha-vms-integrations --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*NxWitness VMS and Hanwha VMS Integrations*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "NxWitness VMS and Hanwha VMS Integrations" 2>$null
How to fix CVE-2026-20801
Upgrade NxWitness VMS and Hanwha VMS Integrations 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 nxwitness-vms-and-hanwha-vms-integrations
dpkg -s nxwitness-vms-and-hanwha-vms-integrations | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh nxwitness-vms-and-hanwha-vms-integrations -y
# or for older releases:
sudo yum update nxwitness-vms-and-hanwha-vms-integrations -y
rpm -q nxwitness-vms-and-hanwha-vms-integrations
SUSE / openSUSE
sudo zypper refresh
sudo zypper update nxwitness-vms-and-hanwha-vms-integrations
rpm -q nxwitness-vms-and-hanwha-vms-integrations
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-20801 affecting NxWitness VMS and Hanwha VMS Integrations
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-20801-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 "*NxWitness VMS and Hanwha VMS Integrations*" -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\nxwitness-vms-and-hanwha-vms-integrations-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\NxWitness VMS and Hanwha VMS Integrations" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "NxWitness VMS and Hanwha VMS Integrations" --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 "NxWitness VMS and Hanwha VMS Integrations"
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-20801 affecting NxWitness VMS and Hanwha VMS Integrations
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-20801-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 nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null | grep -i ^Version || echo "nxwitness-vms-and-hanwha-vms-integrations not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q nxwitness-vms-and-hanwha-vms-integrations || echo "nxwitness-vms-and-hanwha-vms-integrations not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-20801-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/nxwitness-vms-and-hanwha-vms-integrations /etc/nxwitness-vms-and-hanwha-vms-integrations.d /etc/nxwitness-vms-and-hanwha-vms-integrations.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 nxwitness-vms-and-hanwha-vms-integrations
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y nxwitness-vms-and-hanwha-vms-integrations
elif command -v yum >/dev/null; then
yum update -y nxwitness-vms-and-hanwha-vms-integrations
elif command -v zypper >/dev/null; then
zypper --non-interactive update nxwitness-vms-and-hanwha-vms-integrations
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q nxwitness-vms-and-hanwha-vms-integrations
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-20801" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-20801"
Disable the affected service (Linux)
sudo systemctl stop nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null || true
sudo systemctl disable nxwitness-vms-and-hanwha-vms-integrations 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 nxwitness-vms-and-hanwha-vms-integrations 2>/dev/null | grep -i ^Version
rpm -q nxwitness-vms-and-hanwha-vms-integrations 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 "*NxWitness VMS and Hanwha VMS Integrations*" | 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-39387: Cwe-98: improper control of filename for in BoidCMS — Cwe-98: improper control of filename for in BoidCMS
- How to Fix CVE-2026-2064: Critical Vulnerability in i-Educar — Critical Vulnerability in i-Educar
- How to Fix CVE-2026-6437: Cwe-88: improper neutralization of argument delimiters flaw in AWS EFS CSI Driver , Cwe-88: improper neutralization of argument delimiters flaw in AWS EFS CSI Driver
- How to Fix CVE-2026-5972: MetaGPT (Bundle Sibling) , MetaGPT (Bundle Sibling)
- How to Fix CVE-2026-33000: Command Injection in UniFi OS Server , Command Injection in UniFi OS Server
Is CVE-2026-20801 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-20801?
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-20801?
5.6 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L.
Where is the official advisory for CVE-2026-20801?
The vendor advisory is at https://security.gallagher.com/en-NZ/Security-Advisories/CVE-2026-20801. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-20801.
References
- Official vendor advisory: https://security.gallagher.com/en-NZ/Security-Advisories/CVE-2026-20801
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20801
- 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.*