● Critical · CVSS 9.3

How to Fix CVE-2026-26341: Cwe-1392 use of default credentials in Smart+

Q: What is the CVSS score for CVE-2026-26341?

9.3 (Critical). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`.

Q: Where is the official advisory for CVE-2026-26341?

The vendor advisory is at [https://www.zeroscience.mk/en/vulnerabilities/ZSL-2026-5977.php](https://www.zeroscience.mk/en/vulnerabilities/ZSL-2026-5977.php). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-26341.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-26341 is a cwe-1392 use of default credentials in Tattile s.r.l. Smart+. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	9.3 (Critical)
Actively exploited?	No public listing in CISA KEV
Affected	Smart+ 0 to <=1.181.5; Tolling+ 0 to <=1.181.5; Smart+ Speed 0 to <=1.181.5; Smart+ Traffic Light 0 to <=1.181.5; Axle Counter 0 to <=1.181.5; Vega53 0 to <=1.181.5
Fixed in	See vendor advisory
Type (CWE)	CWE-1392 Use of Default Credentials

What is CVE-2026-26341?

Tattile Smart+, Vega, and Basic device families firmware versions 1.181.5 and prior ship with default credentials that are not forced to be changed during installation or commissioning. An attacker who can reach the management interface can authenticate using the default credentials and gain administrative access, enabling unauthorized access to device configuration and data. The CVSS base score is 9.3 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://www.zeroscience.mk/en/vulnerabilities/ZSL-2026-5977.php.

Am I affected?

Check the version of Smart+ you are running and compare it against the Affected row above (Smart+ 0 to <=1.181.5; Tolling+ 0 to <=1.181.5; Smart+ Speed 0 to <=1.181.5; Smart+ Traffic Light 0 to <=1.181.5; Axle Counter 0 to <=1.181.5; Vega53 0 to <=1.181.5). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s smart 2>/dev/null | grep -i ^Version
rpm -q smart 2>/dev/null
command -v smart >/dev/null && smart --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Smart+*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Smart+" 2>$null

How to fix CVE-2026-26341

Upgrade Smart+ 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 smart
dpkg -s smart | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh smart -y
# or for older releases:
sudo yum update smart -y
rpm -q smart

SUSE / openSUSE


sudo zypper refresh
sudo zypper update smart
rpm -q smart

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-26341 affecting Smart+
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-26341-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 "*Smart+*" -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\smart-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Smart+" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Smart+" --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 "Smart+"
    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-26341 affecting Smart+
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-26341-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 smart 2>/dev/null | grep -i ^Version || echo "smart not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q smart || echo "smart not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-26341-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/smart /etc/smart.d /etc/smart.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 smart
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y smart
elif command -v yum >/dev/null; then
    yum update -y smart
elif command -v zypper >/dev/null; then
    zypper --non-interactive update smart
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s smart 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q smart
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-26341" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-26341"

Disable the affected service (Linux)


sudo systemctl stop smart 2>/dev/null || true
sudo systemctl disable smart 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 smart 2>/dev/null | grep -i ^Version
rpm -q smart 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 "*Smart+*" | 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

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-23683: Critical Vulnerability in SAP Fiori App (Intercompany Balance Reconciliation) — Critical Vulnerability in SAP Fiori App (Intercompany Balance Reconciliation)
How to Fix CVE-2026-20203: The software does not restrict or in Splunk Cloud Platform — The software does not restrict or in Splunk Cloud Platform
How to Fix CVE-2026-33207: SQL injection in dataease , SQL injection in dataease
How to Fix CVE-2026-5243: Cross-Site Scripting in The Plus Addons for Elementor – Addons for Elementor, Page Templates, Widgets, Mega Menu, WooCommerce , Cross-Site Scripting in The Plus Addons for Elementor – Addons for Elementor, Page Templates, Widgets, Mega Menu, WooCommerce
How to Fix CVE-2026-8203: Cross-Site Scripting in Concrete CMS , Cross-Site Scripting in Concrete CMS

Is CVE-2026-26341 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-26341?

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-26341?

9.3 (Critical). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.

Where is the official advisory for CVE-2026-26341?

The vendor advisory is at https://www.zeroscience.mk/en/vulnerabilities/ZSL-2026-5977.php. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-26341.

References

Official vendor advisory: https://www.zeroscience.mk/en/vulnerabilities/ZSL-2026-5977.php
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26341
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://www.tattile.com/
Additional reference: https://www.vulncheck.com/advisories/tattile-smart-vega-basic-default-credentials

*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.*