● Medium · CVSS 4.3

How to Fix CVE-2026-27695: Resource exhaustion in zae-limiter

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

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

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

The vendor advisory is at [https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6](https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27695.

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

CVE-2026-27695 is a resource exhaustion in zeroae zae-limiter. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	4.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	zae-limiter < 0.10.1
Fixed in	See vendor advisory
Type (CWE)	CWE-770: Allocation of Resources Without Limits or Throttling

What is CVE-2026-27695?

zae-limiter is a rate limiting library using the token bucket algorithm. Prior to version 0.10.1, all rate limit buckets for a single entity share the same DynamoDB partition key (namespace/ENTITY#{id}). A high-traffic entity can exceed DynamoDB's per-partition throughput limits (~1, 000 WCU/sec), causing throttling that degrades service for that entity — and potentially co-located entities in the same partition. Version 0.10.1 fixes the issue. The CVSS base score is 4.3 (Medium). The official advisory is at https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6.

Am I affected?

Check the version of zae-limiter you are running and compare it against the Affected row above (zae-limiter < 0.10.1). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-27695

Upgrade zae-limiter 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 zae-limiter
dpkg -s zae-limiter | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update zae-limiter
rpm -q zae-limiter

Node.js / npm


# Update the affected package in your project
npm install zae-limiter@latest
npm ls zae-limiter
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27695 affecting zae-limiter
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

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

Disable the affected service (Linux)


sudo systemctl stop zae-limiter 2>/dev/null || true
sudo systemctl disable zae-limiter 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 zae-limiter 2>/dev/null | grep -i ^Version
rpm -q zae-limiter 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 "*zae-limiter*" | 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-27076: Critical Vulnerability in LuxeDrive — Critical Vulnerability in LuxeDrive
How to Fix CVE-2026-41505: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in relate , Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in relate
How to Fix CVE-2026-30701: n/a in n/a , n/a in n/a
How to Fix CVE-2026-27491: Discourse has a bypass of official warnings messages by non-staff users , Discourse has a bypass of official warnings messages by non-staff users
How to Fix CVE-2026-5271: Possible to hijack modules in current working directory in pymanager , Possible to hijack modules in current working directory in pymanager

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

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

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

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

The vendor advisory is at https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27695.

References

Official vendor advisory: https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27695
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/zeroae/zae-limiter/releases/tag/v0.10.1

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