CVE-2026-44981: CrowdSec Local API (LAPI) Denial of Service via Gzip Decompression Bomb
HERMES THREAT SCORE & PERIMETER DEFENSE DISRUPTION EVALUATION
Target:CrowdSec Security Engine โ Local API Router (pkg/apiserver) NVD and initial CVE metrics score CVE-2026-44981 between 7.5 and 8.2 (High) under CVSS v3.1, treating the issue as a generic unauthenticated denial of service. The Hermes Threat Score elevates this assessment to 90 (CRITICAL) because active in-the-wild exploitation campaigns have been flagged by CrowdSec CTI honeypots. In multi-server enterprise perimeters and cloud clusters, the CrowdSec Local API (LAPI) coordinates threat decisions, real-time IP bans, and consensus signals across downstream remediation bouncers (Nginx, Traefik, HAProxy, iptables, and CrowdSec AppSec WAF). Forcing an Out-Of-Memory (OOM) termination on LAPI blinds the entire perimeter intrusion prevention mesh, preventing new attacker IPs from being blocked and allowing secondary exploitation chains to execute unimpeded.
CVE-2026-44981: CrowdSec Local API (LAPI) Denial of Service via Gzip Decompression BombVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in CrowdSec Security Engine & AppSec WAF documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโCrowdSec operates as a modern collaborative intrusion prevention system (IPS). In distributed architectures, machines host remediation bouncers while routing signals to a centralized or containerized CrowdSec Local API (LAPI) instance.
| Parameter | Technical Specification | Operational Details |
|---|---|---|
| CVE Identifier | CVE-2026-44981 | Global vulnerability tracking identifier |
| Software Platform | CrowdSec Security Engine | Open-source collaborative IDS/IPS & AppSec WAF |
| Vulnerable Component | pkg/apiserver/router.go (gin-contrib/gzip) | LAPI HTTP ingestion middleware |
| Vulnerability Class | CWE-409 / CWE-770 / CWE-400 | Decompression Bomb / Unbounded Resource Allocation |
| Attack Vector | Network (Port 8080 TCP / LAPI interface) | Remote, unauthenticated HTTP POST with Content-Encoding: gzip |
| Fixed Version | CrowdSec v1.7.8 | Enforces http.MaxBytesReader limit on decompressed streams |
[ Unauthenticated Attacker ] | Crafted Gzip Payload (4 KB wire size, 4 GB decompressed) Header: Content-Encoding: gzip | v +------------------------------------------+ | CrowdSec LAPI Router (Port 8080 TCP) | | pkg/apiserver/router.go | +------------------------------------------+ | [ gin-contrib/gzip Middleware ] No decompressed size limiter! | v +------------------------------------------+ | Go Runtime Heap Allocation | | Allocates > 8 GB RAM in seconds | +------------------------------------------+ | v +------------------------------------------+ | Linux Kernel OOM Killer | | SIGKILL -> crowdsec process dies | +------------------------------------------+ | +----------------------+----------------------+ | | v v [ Ingress Bouncers Blinded ] [ Threat Intel Feed Frozen ] Nginx / Traefik / WAF stop blocking No blocklist updates distributed2. Root Cause Analysis & Vulnerable Code Anatomy
Section titled โ2. Root Cause Analysis & Vulnerable Code AnatomyโThe root cause of CVE-2026-44981 is the absence of a size-limiting reader wrapper around the decompressed HTTP body reader in the Gin web framework router configuration within pkg/apiserver.
In Go web services, gin-contrib/gzip replaces c.Request.Body with a gzip.Reader. However, reading directly from gzip.Reader without wrapping it in http.MaxBytesReader allows an input stream to read indefinitely until EOF:
// Vulnerable LAPI setup in pkg/apiserver/router.go (CrowdSec < 1.7.8)func (s *APIServer) initRouter() (*gin.Engine, error) { router := gin.New()
// Gzip middleware applied globally without decompressed limit router.Use(gzip.Gzip(gzip.DefaultCompression))
// Unauthenticated routes exposed to external network watchers v1 := router.Group("/v1") { v1.POST("/watchers", s.controller.CreateWatcher) v1.POST("/watchers/login", s.controller.AuthenticateWatcher) }
return router, nil}When an attacker connects to /v1/watchers or /v1/watchers/login, the request body is parsed into a Go struct using c.ShouldBindJSON(&watcher). The JSON decoder reads the entire uncompressed stream into memory buffers. Because the compression ratio of repetitive zero-byte or space-padded JSON structures can exceed 1000:1, a 4 MB HTTP request payload expands into over 4 GB of heap allocations.
In CrowdSec 1.7.8, the engineering team introduced strict size limits via http.MaxBytesReader and configured body reader caps prior to decompression:
// Patched LAPI stream handling in CrowdSec 1.7.8func LimitBodySize(maxBytes int64) gin.HandlerFunc { return func(c *gin.Context) { c.Request.Body = http.MaxBytesReader(c.Writer, c.Request.Body, maxBytes) c.Next() }}3. Threat Weaponization Mechanics & Attack Execution Flow
Section titled โ3. Threat Weaponization Mechanics & Attack Execution FlowโThreat actors exploit CVE-2026-44981 to neutralize detection before launching noisy attacks against protected services behind CrowdSec bouncers.
sequenceDiagram autonumber actor Attacker as Threat Actor participant LAPI as CrowdSec LAPI (:8080) participant Kernel as Linux Kernel / OOM participant Bouncer as Nginx / Traefik Bouncer participant App as Protected Web Backend
Attacker->>LAPI: POST /v1/watchers (Content-Encoding: gzip, 32KB payload) Note over LAPI: gzip.Reader inflates payload to 4.2 GB in memory LAPI->>LAPI: JSON parser exhausts Go runtime heap Kernel->>LAPI: OOM Killer triggers: SIGKILL pid crowdsec Note over LAPI: CrowdSec daemon crashes and ceases listening Attacker->>App: Launch credential stuffing / SQLi / zero-day exploits Bouncer-->>LAPI: Query live IP remediation decisions (Connection Refused) Note over Bouncer: Bouncer fails open / serves cached rules without updates Attacker->>App: Exploitation succeeds without automated perimeter blockingAttack Vector Characteristics
Section titled โAttack Vector Characteristicsโ- Pre-authentication reachability: The
/v1/watchersand/v1/watchers/loginendpoints must accept requests from unauthenticated clients registering new machine agents or obtaining JWT session tokens. - Minimal bandwidth requirement: An attacker requires fewer than 100 requests of 32 KB each over a 5-second interval to exhaust 16 GB to 32 GB of system memory.
- Fail-open bouncer behavior: When LAPI stops responding, many remediation bouncers (such as Nginx Lua plugins or iptables bouncers) log connectivity errors but continue passing web traffic to maintain application availability.
4. Forensic Investigation & Threat Hunting
Section titled โ4. Forensic Investigation & Threat HuntingโDetecting CVE-2026-44981 requires monitoring reverse proxy logs for compressed requests to LAPI, system log inspection for kernel OOM events, and process crash audits.
title: CrowdSec LAPI Decompression Bomb Denial of Serviceid: 8b73a412-2d1e-4f01-9a74-44981e11a001status: experimentaldescription: Detects suspicious gzip-compressed POST requests to unauthenticated CrowdSec LAPI watcher endpoints indicative of CVE-2026-44981 exploitation.references: - https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-273h-gvwr-c3qj - https://hermes-codex.vercel.app/cve/2026/cve-2026-44981/author: Hermes Codex Cyber Intelligencedate: 2026-10-06logsource: category: webserver product: nginxdetection: selection_endpoint: cs-method: POST cs-uri-stem|startswith: - '/v1/watchers' - '/v1/watchers/login' selection_headers: cs-header-content-encoding|contains: 'gzip' condition: selection_endpoint and selection_headersfalsepositives: - Legitimate automated client scripts explicitly compressing watcher registration requests (rare)level: hightags: - attack.impact - attack.t1499.004// Detect CrowdSec process termination via Linux Kernel OOM killerSyslog| where Facility == "kern" or ProcessName == "kernel"| where SyslogMessage has "Out of memory: Kill process" and SyslogMessage has "crowdsec"| extend KilledProcess = extract(@"Kill process (\d+) \(([^)]+)\)", 2, SyslogMessage), KilledPID = extract(@"Kill process (\d+)", 1, SyslogMessage), OOMScore = extract(@"score (\d+)", 1, SyslogMessage)| project TimeGenerated, HostName, KilledProcess, KilledPID, OOMScore, SyslogMessage| order by TimeGenerated desc#!/usr/bin/env bash# Quick forensic verification of CrowdSec LAPI OOM crashesecho "[*] Checking Linux kernel dmesg for OOM killer invocations..."dmesg -T | grep -i -E "oom-killer|killed process.*crowdsec" || echo "[-] No OOM kill found in current kernel ring buffer."
echo "[*] Auditing systemd service status for crowdsec..."systemctl status crowdsec.service --no-pager
echo "[*] Checking CrowdSec log for abrupt terminations..."if [ -f "/var/log/crowdsec.log" ]; then tail -n 50 /var/log/crowdsec.logfi
echo "[*] Checking journalctl for SIGKILL events on crowdsec..."journalctl -u crowdsec -n 30 --no-pager5. Remediation Strategy & Mitigation
Section titled โ5. Remediation Strategy & Mitigationโ-
Upgrade CrowdSec to v1.7.8 or later: Upgrade all CrowdSec Security Engine nodes immediately using the official repositories:
Terminal window sudo apt-get update && sudo apt-get --only-upgrade install crowdsec# On RHEL/AlmaLinux/Rocky Linux:sudo dnf upgrade crowdsec -
Restrict LAPI Network Exposure: Ensure LAPI only listens on localhost (
127.0.0.1) if all bouncers run on the same host:/etc/crowdsec/config.yaml api:server:listen_uri: 127.0.0.1:8080If LAPI must be accessible across a fleet, restrict access via firewall rules (UFW/nftables/AWS Security Groups) exclusively to known bouncer IP addresses.
-
Configure Upstream Reverse Proxy Request Limits: If exposing LAPI through Nginx, disable decompression pass-through and enforce body size limits:
location /v1/watchers {client_max_body_size 1m;proxy_pass http://127.0.0.1:8080;}