Skip to content

CVE-2026-44982: CrowdSec AppSec WAF Partial Inspection Bypass via Transfer-Encoding Chunked and HTTP/2 Framing

Density:
HERMES

HERMES THREAT SCORE & PERIMETER GATEWAY DEFENSE EVALUATION

Target: CrowdSec Security Engine - AppSec WAF Inspection Engine (pkg/appsec)
Confidence: 98%
91 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 18 / 20
Weaponization 18 / 20
Exposure 19 / 20
Prevalence 17 / 20
Impact 18 / 20
Exploit Maturity 18 / 20
Attack Chain Potential 19 / 20
โš–๏ธ Divergence & Operational Rationale

NVD and generic vulnerability scoring models evaluate this flaw between 7.2 and 8.6, considering it solely as an inspection engine failure. The Hermes Threat Score elevates this assessment to 91 (CRITICAL) based on active in-the-wild threat campaigns identified by CrowdSec CTI telemetry. In enterprise perimeter architectures, CrowdSec AppSec operates as an inline reverse-proxy defense layer guarding backend application servers. A silent body-inspection bypass blinds all ModSecurity and AppSec rule evaluations (REQUEST_BODY, ARGS_POST, JSON, XML), enabling attackers to route malicious SQLi, command injection, and deserialization exploits directly to internal backends without triggering security alerts.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-44982: CrowdSec AppSec WAF Partial Inspection Bypass via Transfer-Encoding Chunked and HTTP/2 FramingVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTCrowdSec Security Engine & AppSec WAF
98% VERY_HIGH

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

Supporting Verified Evidence:

CrowdSec Security Engine is an open-source, collaborative intrusion detection and prevention system widely deployed as an ingress controller, API gateway filter, and reverse-proxy WAF (via Nginx, Traefik, HAProxy, and OpenResty remediation bouncers).

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-44982International security tracking reference
Vendor / EcosystemCrowdSecOpen-Source Collaborative Cyber Defense
Vulnerable Componentpkg/appsec/request.go (NewParsedRequestFromRequest)AppSec datasource parsing pipeline
Flaw ClassificationCWE-670 / CWE-693 / CWE-436Control Flow Implementation / WAF Bypass
Attack VectorNetwork (Port 80/443 TCP)Remote, unauthenticated HTTP/1.1 & HTTP/2 requests
Remediation ReleaseCrowdSec v1.7.8Mandatory software update across all nodes
Remediation BouncersNginx & OpenResty Bouncers (Latest)Component sync required to eliminate bypass

In Goโ€™s net/http implementation, incoming HTTP requests populate the http.Request struct. When a request defines a standard content length, r.ContentLength reflects that integer value. However, when an HTTP/1.1 client streams data using Transfer-Encoding: chunked, or when an HTTP/2 connection sends data frames without a Content-Length header, r.ContentLength is set to -1 to denote an undefined body stream length.

In vulnerable versions of CrowdSec prior to 1.7.8, the function NewParsedRequestFromRequest inside pkg/appsec/request.go attempted to allocate an internal byte buffer for AppSec inspection rules:

// Vulnerable Implementation in pkg/appsec/request.go (< 1.7.8)
func NewParsedRequestFromRequest(r *http.Request) (*ParsedRequest, error) {
pr := &ParsedRequest{
// ... header and URI extraction ...
}
// FLAW: If r.ContentLength is -1 (chunked or HTTP/2), max(-1, 0) == 0!
bodyBuf := make([]byte, max(r.ContentLength, 0))
if r.Body != nil {
_, err := io.ReadFull(r.Body, bodyBuf)
if err != nil && err != io.EOF && err != io.ErrUnexpectedEOF {
return nil, err
}
}
pr.Body = bodyBuf
return pr, nil
}

Because bodyBuf was allocated with a capacity and length of 0, the io.ReadFull(r.Body, bodyBuf) call immediately succeeded having read exactly zero bytes. The remaining body stream remained unread by AppSec, and pr.Body was saved as an empty slice []byte{}.

UNAUTHENTICATED ATTACKER
โ”‚
โ”‚ [1] Send HTTP/1.1 POST with "Transfer-Encoding: chunked"
โ”‚ Body: "union select username,password from users--"
โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ CROWDSEC APPSEC INLINE WAF โ”‚
โ”‚ โ”‚
โ”‚ โ€ข Evaluates r.ContentLength == -1 โ”‚
โ”‚ โ€ข Executes make([]byte, max(-1, 0)) -> make([]byte, 0)โ”‚
โ”‚ โ€ข Reads 0 bytes from request stream โ”‚
โ”‚ โ€ข AppSec Engine: Evaluates rules against empty body: โ”‚
โ”‚ - REQUEST_BODY: "" -> [NO MATCH] โ”‚
โ”‚ - ARGS_POST: {} -> [NO MATCH] โ”‚
โ”‚ - JSON / XML: {} -> [NO MATCH] โ”‚
โ”‚ โ€ข Result: Decision = "ALLOW", Threat Score = 0 โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
โ”‚
โ”‚ [2] Forward uninspected request to upstream
โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ UPSTREAM BACKEND APPLICATION โ”‚
โ”‚ โ€ข HTTP server decodes chunked payload โ”‚
โ”‚ โ€ข Executes SQL injection in database context โ”‚
โ”‚ โ€ข FULL COMPROMISE (Zero CrowdSec alerts triggered) โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

In CrowdSec 1.7.8, the AppSec request ingestion logic was rewritten to check whether r.ContentLength < 0 or read via io.ReadAll with an explicit memory ceiling (maxBodySize), ensuring that chunked and HTTP/2 payloads are fully materialized into memory before rule evaluation:

// Patched Implementation in pkg/appsec/request.go (>= 1.7.8)
func NewParsedRequestFromRequest(r *http.Request, maxBodySize int64) (*ParsedRequest, error) {
pr := &ParsedRequest{
// ...
}
if r.Body != nil {
limitedReader := io.LimitReader(r.Body, maxBodySize)
bodyBytes, err := io.ReadAll(limitedReader)
if err != nil {
return nil, fmt.Errorf("failed to read request body: %w", err)
}
pr.Body = bodyBytes
// Restore r.Body for downstream remediation bouncers if needed
r.Body = io.NopCloser(bytes.NewReader(bodyBytes))
}
return pr, nil
}

Threat actors actively targeting perimeter gateways exploit this flaw to execute defense evasion against web applications guarded by CrowdSec:

  1. Blind SQL Injection via Chunked Encoding: Attackers issue POST requests to public forms using Transfer-Encoding: chunked. Any AppSec rules inspecting SQL injection keywords (UNION, SELECT, ' OR 1=1) look exclusively at ARGS_POST and REQUEST_BODY. Because those fields are empty, the WAF forwards the request cleanly.
  2. Remote Code Execution via Deserialization or Multipart Payloads: When exploiting backend flaws like deserialization or fast-acting RCE chains, the attacker uses HTTP/2 streams without a Content-Length header. The exploit lands directly in the backend runtime.
  3. Absence of Forensic Alerting: Because the WAF rules evaluate to false, CrowdSec does not generate alerts, does not increment the IPโ€™s threat score in the Local API (LAPI), and does not share attack telemetry with the CrowdSec Consensus Community.

title: Potential CrowdSec AppSec WAF Bypass Attempt via Chunked Transfer-Encoding
id: cve-2026-44982-crowdsec-bypass
status: experimental
description: Detects inbound POST/PUT requests using Transfer-Encoding chunked targeting web applications, a technique used to evade CrowdSec AppSec body inspection prior to v1.7.8.
author: Hermes Codex Cyber Threat Intelligence
date: 2026-09-27
references:
- https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-79v8-67p5-2h8g
tags:
- attack.defense_evasion
- attack.t1562.001
logsource:
category: webserver
product: nginx
detection:
selection:
cs_method:
- 'POST'
- 'PUT'
- 'PATCH'
cs_header_transfer_encoding|contains: 'chunked'
condition: selection
falsepositives:
- Legitimate API clients uploading large streaming media or telemetry batches.
level: medium

  1. Upgrade CrowdSec Security Engine: Immediately update all CrowdSec instances to version 1.7.8 or later using the official package repositories:

    Terminal window
    sudo apt-get update && sudo apt-get install --only-upgrade crowdsec
    sudo systemctl restart crowdsec
  2. Update Remediation Components: Ensure that remediation bouncers (specifically crowdsec-nginx-bouncer, crowdsec-openresty-bouncer, and Kubernetes Ingress Controllers) are updated to the latest available releases to support full body buffering.

  3. Enforce Ingress Reverse Proxy Restrictions: If upgrading CrowdSec requires staging, configure front-facing load balancers (such as Cloudflare or Nginx) to enforce HTTP Content-Length headers and buffer chunked requests before handing them off to internal microservices:

    # Disable chunked transfer-encoding pass-through on sensitive APIs
    client_max_body_size 10M;
    chunked_transfer_encoding on; # Ensure Nginx re-buffers before forwarding