● Low · CVSS 3.8

How to Fix CVE-2026-32715: CWE-863: Incorrect Authorization in anything-llm

Q: Is CVE-2026-32715 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-32715?

CVSS rates it 3.8 (Low). Use that score to set your patch priority next to the other items in your queue.

Q: Do I have to take anything-llm offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-32715 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

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

How to Fix CVE-2026-44479: Information Disclosure in vercel — Information Disclosure in vercel
How to Fix CVE-2026-2147: Information Disclosure in AC21 — Information Disclosure in AC21
How to Fix CVE-2026-22323: Cross‑Site Request Forgery in Link Aggregation Configuration , Cross‑Site Request Forgery in Link Aggregation Configuration
How to Fix CVE-2026-3194: Missing authentication in Blockchain , Missing authentication in Blockchain
How to Fix CVE-2026-0383: Command Injection in Fabric OS , Command Injection in Fabric OS

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 3.8, Low
Actively exploited?	No
Affected	Mintplex-labs anything-llm (<= 1.11.1)
Fixed in	See vendor advisory
Type (CWE)	CWE-863: Incorrect Authorization

What is CVE-2026-32715?

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, The two generic system-preferences endpoints allow manager role access, while every other surface that touches the same settings is restricted to admin only. Because of this inconsistency, a manager can call the generic endpoints directly to read plaintext SQL database credentials and overwrite admin-only global settings such as the default system prompt and the Community Hub API key.

In practical terms, a successful attacker gets compromise of the affected component as described in the vendor advisory. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You're affected if you run Mintplex-labs anything-llm at any version in the Affected row above. Use these probes to find your installed build:


# Confirm the installed version via your package manager
dpkg -l | grep -i anything-llm   # Debian/Ubuntu
rpm -qa | grep -i anything-llm   # RHEL/CentOS/Rocky

How to fix CVE-2026-32715

The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
sudo apt-get update
sudo apt-get install --only-upgrade anything-llm
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s anything-llm | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security anything-llm -y
rpm -q anything-llm

Windows (PowerShell, admin)


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
# Try winget first
winget upgrade --id 'Mintplex-labs.anything-llm' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\anythingllm-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\anythingllm-Patch-CVE-2026-32715.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-32715 remediation for Mintplex-labs anything-llm"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*anything-llm*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\anythingllm-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Mintplex-labs\anything-llm"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\anythingllm-<patched-version>.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*anything-llm*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/anything-llm-patch-cve-2026-32715.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-32715 remediation for Mintplex-labs anything-llm"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s anything-llm >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' anything-llm)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q anything-llm >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' anything-llm)
    PKG_MGR=dnf
else
    log "anything-llm not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: anything-llm=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/anything-llm-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/anything-llm /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y anything-llm
else
    sudo dnf upgrade --security -y anything-llm
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' anything-llm)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' anything-llm)
fi
log "After upgrade: $NEW"

# Optionally compare against <patched-version> with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

No official vendor workaround is published for this CVE; patching is the only documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.

Restrict the affected service to trusted networks (Linux):


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
# Replace <port> with the affected service port and 10.0.0.0/24 with your admin subnet
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP

Windows Firewall equivalent:


# Vendor advisory: https://github.com/Mintplex-Labs/anything-llm/security/advisories/GHSA-wfq3-65gm-3g2p
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' \
    -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' \
    -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "anything-llm"   # Debian/Ubuntu
rpm -qa | grep -i "anything-llm"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed the patched build.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-32715 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-32715 being actively exploited?