● Low · CVSS 2.3

How to Fix CVE-2026-23983: Information exposure in Apache Superset

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

2.3 (Low). Vector: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`.

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

The vendor advisory is at [https://lists.apache.org/thread/62mgbc5hc8026skp69kb6vqozj3pr5ww](https://lists.apache.org/thread/62mgbc5hc8026skp69kb6vqozj3pr5ww). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-23983.

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

CVE-2026-23983 is a information exposure in Apache Software Foundation Apache Superset. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	2.3 (Low)
Actively exploited?	No public listing in CISA KEV
Affected	Apache Superset 0.0.0 to <6.0.0
Fixed in	See vendor advisory
Type (CWE)	CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

What is CVE-2026-23983?

A Sensitive Data Exposure vulnerability exists in Apache Superset allowing authenticated users to retrieve sensitive user information. The Tag endpoint (disabled by default) allows users to retrieve a list of objects associated with a specific tag.

When these associated objects include Users, the API response improperly serializes and returns sensitive fields, including password hashes (pbkdf2), email addresses, and login statistics. This vulnerability allows authenticated users with low privileges (e.g., Gamma role) to view sensitive authentication data

This issue affects Apache Superset: before 6.0.0.

Users are recommended to upgrade to version 6.0.0, which fixes the issue or make sure TAGGING_SYSTEM is False (Apache Superset current default) The CVSS base score is 2.3 (Low). The official advisory is at https://lists.apache.org/thread/62mgbc5hc8026skp69kb6vqozj3pr5ww.

Am I affected?

Check the version of Apache Superset you are running and compare it against the Affected row above (Apache Superset 0.0.0 to <6.0.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-23983

Upgrade Apache Superset 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 apache-superset
dpkg -s apache-superset | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update apache-superset
rpm -q apache-superset

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-23983 affecting Apache Superset
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

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

Disable the affected service (Linux)


sudo systemctl stop apache-superset 2>/dev/null || true
sudo systemctl disable apache-superset 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 apache-superset 2>/dev/null | grep -i ^Version
rpm -q apache-superset 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 "*Apache Superset*" | 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-40860: Apache Camel (Bundle Sibling) — Apache Camel (Bundle Sibling)
How to Fix CVE-2026-23901: Critical Vulnerability in Apache Shiro — Critical Vulnerability in Apache Shiro
How to Fix CVE-2026-42809: Missing Authorization in Apache Polaris , Missing Authorization in Apache Polaris
How to Fix CVE-2026-33858: Deserialization of untrusted data in Apache Airflow , Deserialization of untrusted data in Apache Airflow
How to Fix CVE-2026-32794: Code Injection RCE in Apache Airflow Provider for Databricks , Code Injection RCE in Apache Airflow Provider for Databricks

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

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

2.3 (Low). Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N.

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

The vendor advisory is at https://lists.apache.org/thread/62mgbc5hc8026skp69kb6vqozj3pr5ww. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-23983.

References

Official vendor advisory: https://lists.apache.org/thread/62mgbc5hc8026skp69kb6vqozj3pr5ww
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23983
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.*