● Medium · CVSS 5.3

How to Fix CVE-2026-2752: Information disclosure via error message in NavBox

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

5.3 (Medium). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`.

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

The vendor advisory is at [https://www.navtor.com/navtor-vendor-statement](https://www.navtor.com/navtor-vendor-statement). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2752.

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

CVE-2026-2752 is a information disclosure via error message in Navtor NavBox. The fix is to upgrade to NavBox 4.16.2.4.

⚡ At a glance


Severity	5.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	NavBox 4.12.0.3
Fixed in	NavBox 4.16.2.4
Type (CWE)	CWE-209 Generation of Error Message Containing Sensitive Information

What is CVE-2026-2752?

Navtor NavBox allows information disclosure via the /api/ais-data endpoint. A remote, unauthenticated attacker can send crafted requests to trigger an unhandled exception, causing the server to return verbose .NET stack traces. These error messages expose internal class names, method calls, and third-party library references (e.g., System.Data.SQLite), which may assist attackers in mapping the application's internal structure. The CVSS base score is 5.3 (Medium). The official advisory is at https://www.navtor.com/navtor-vendor-statement.

Am I affected?

Check the version of NavBox you are running and compare it against the Affected row above (NavBox 4.12.0.3). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-2752

Upgrade NavBox to a patched build: NavBox 4.16.2.4. 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 navbox
dpkg -s navbox | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update navbox
rpm -q navbox

Node.js / npm


# Update the affected package in your project
npm install NavBox@latest
npm ls NavBox
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2752 affecting NavBox
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

    Write-Host "[3/4] Apply the upgrade to NavBox 4.16.2.4"
    winget upgrade --name "NavBox" --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 "NavBox"
    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-2752 affecting NavBox
# Detect -> backup -> upgrade -> verify -> log.

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

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2752-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/navbox /etc/navbox.d /etc/navbox.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: NavBox 4.16.2.4)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y navbox
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y navbox
elif command -v yum >/dev/null; then
    yum update -y navbox
elif command -v zypper >/dev/null; then
    zypper --non-interactive update navbox
fi

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

Disable the affected service (Linux)


sudo systemctl stop navbox 2>/dev/null || true
sudo systemctl disable navbox 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 navbox 2>/dev/null | grep -i ^Version
rpm -q navbox 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 "*NavBox*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above NavBox 4.16.2.4. 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-7776: Allocation of Resources Without Limits or Throttling in Boundary — Allocation of Resources Without Limits or Throttling in Boundary
How to Fix CVE-2026-8238: Missing Authorization in Concrete CMS — Missing Authorization in Concrete CMS
How to Fix CVE-2026-27773: Weak credential storage in swtchenergy.com , Weak credential storage in swtchenergy.com
How to Fix CVE-2026-44577: Denial of Service in next.js , Denial of Service in next.js
How to Fix CVE-2026-0615: Critical Vulnerability in TheLibrarian.io , Critical Vulnerability in TheLibrarian.io

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

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

5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.

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

The vendor advisory is at https://www.navtor.com/navtor-vendor-statement. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2752.

References

Official vendor advisory: https://www.navtor.com/navtor-vendor-statement
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2752
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://cydome.io/vulnerability-advisory-cve-2026-2752-in-navtor-navbox-version-4-12-0-3

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