How to Fix CVE-2026-1775: Missing authentication in LID-3300IP
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-1775 is a missing authentication in Labkotec LID-3300IP. The fix is to apply the vendor patch noted below.
| Severity | 8.8 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | LID-3300IP All versions; LID-3300IP Type 2 0 to <2.20 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-306 Missing Authentication for Critical Function |
What is CVE-2026-1775?
The Labkotec LID-3300IP has an existing vulnerability in the ice detector software that enables an unauthenticated attacker to alter device parameters and run operational commands when specially crafted packets are sent to the device. The CVSS base score is 8.8 (High), 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-062-05.
Am I affected?
Check the version of LID-3300IP you are running and compare it against the Affected row above (LID-3300IP All versions; LID-3300IP Type 2 0 to <2.20). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s lid-3300ip 2>/dev/null | grep -i ^Version
rpm -q lid-3300ip 2>/dev/null
command -v lid-3300ip >/dev/null && lid-3300ip --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*LID-3300IP*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "LID-3300IP" 2>$null
How to fix CVE-2026-1775
Upgrade LID-3300IP 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 lid-3300ip
dpkg -s lid-3300ip | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh lid-3300ip -y
# or for older releases:
sudo yum update lid-3300ip -y
rpm -q lid-3300ip
SUSE / openSUSE
sudo zypper refresh
sudo zypper update lid-3300ip
rpm -q lid-3300ip
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-1775 affecting LID-3300IP
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-1775-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 "*LID-3300IP*" -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\lid-3300ip-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\LID-3300IP" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "LID-3300IP" --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 "LID-3300IP"
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-1775 affecting LID-3300IP
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-1775-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 lid-3300ip 2>/dev/null | grep -i ^Version || echo "lid-3300ip not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q lid-3300ip || echo "lid-3300ip not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-1775-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/lid-3300ip /etc/lid-3300ip.d /etc/lid-3300ip.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 lid-3300ip
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y lid-3300ip
elif command -v yum >/dev/null; then
yum update -y lid-3300ip
elif command -v zypper >/dev/null; then
zypper --non-interactive update lid-3300ip
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s lid-3300ip 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q lid-3300ip
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-1775" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-1775"
Disable the affected service (Linux)
sudo systemctl stop lid-3300ip 2>/dev/null || true
sudo systemctl disable lid-3300ip 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 lid-3300ip 2>/dev/null | grep -i ^Version
rpm -q lid-3300ip 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 "*LID-3300IP*" | 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-8262: Cross Site Scripting in ERP Online — Cross Site Scripting in ERP Online
- How to Fix CVE-2026-0830: Command Injection in Kiro IDE — Command Injection in Kiro IDE
- How to Fix CVE-2026-27361: Missing authorization in Responsive Posts Carousel Pro , Missing authorization in Responsive Posts Carousel Pro
- How to Fix CVE-2026-29063: Improperly controlled modification of object prototype attributes ('prototype. , Improperly controlled modification of object prototype attributes ('prototype.
- How to Fix CVE-2026-3040: Os command injection in Vigor 300B , Os command injection in Vigor 300B
Is CVE-2026-1775 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-1775?
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-1775?
8.8 (High). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N.
Where is the official advisory for CVE-2026-1775?
The vendor advisory is at https://www.cisa.gov/news-events/ics-advisories/icsa-26-062-05. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-1775.
References
- Official vendor advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-26-062-05
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1775
- 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.*