⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.5

How to Fix CVE-2026-40879: Cwe-674: uncontrolled recursion in nest

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

⚡ At a glance
Severity7.5 (High)
Actively exploited?No public listing in CISA KEV
Affectednestjs < 11.1.19
Fixed innest 11.1.19
Type (CWE)CWE-674: CWE-674: Uncontrolled Recursion

What is CVE-2026-40879?

Nest is a framework for building scalable Node.js server-side applications. Prior to 11.1.19, when an attacker sends many small, valid JSON messages in one TCP frame, handleData() recurses once per message; the buffer shrinks each call. maxBufferSize is never reached; call stack overflows instead. A ~47 KB payload is sufficient to trigger RangeError.

Am I affected?

Run the version check that matches your platform:


# Linux
dpkg -s nest 2>/dev/null | grep -i version
rpm -q nest 2>/dev/null
nest --version 2>/dev/null

Compare what you see against the Affected row above (nestjs < 11.1.19). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-40879

The primary fix is to upgrade nest to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: nest 11.1.19.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade nest
nest --version 2>/dev/null || dpkg -s nest | grep -i version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --security nest -y
rpm -q nest

SUSE / openSUSE


sudo zypper patch --category security
rpm -q nest

Complete PowerShell remediation script (Windows)


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

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-40879-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] Detecting installed version of nest"
    $pkg = winget list --id "nest" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up configuration"
    $backup = "C:\Backup\nest-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\nest" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Applying upgrade to nest 11.1.19"
    winget upgrade --id "nest" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "nest"
    Write-Host "Fix 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-40879 affecting nest
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-40879-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s nest 2>/dev/null | grep -i version || echo "nest not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q nest || echo "nest not installed via rpm"
fi

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

echo "[3/4] Applying upgrade (target: nest 11.1.19)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y nest
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y nest
elif command -v yum >/dev/null; then
    yum update -y nest
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s nest 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q nest
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)


# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback


# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop nest
sudo systemctl disable nest

How to verify the fix worked


# Linux
nest --version 2>/dev/null || dpkg -s nest | grep -i version
rpm -q nest 2>/dev/null || true


# Windows
winget list | findstr /I "nest"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above nest 11.1.19. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

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

Is CVE-2026-40879 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

7.5 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

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