CVE-2026-44982

CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests

Published Jul 16, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Description
CrowdSec offers crowdsourced protection against malicious IPs. From 1.5.0 until 1.7.8, pkg/appsec/request.go NewParsedRequestFromRequest allocated a request body buffer from max(r.ContentLength, 0), so HTTP/1.1 requests using Transfer-Encoding: chunked and HTTP/2 requests without a content-length header produced an empty body and caused WAF rules targeting REQUEST_BODY, BODY_ARGS, ARGS_POST, JSON, or XML to be skipped. This issue is fixed in version 1.7.8.

Analysis

AI-generated

Technical impact

The vulnerability arises from CrowdSec's request parsing logic in NewParsedRequestFromRequest, which allocates its request body buffer using max(r.ContentLength, 0). For HTTP/1.1 requests that use Transfer-Encoding: chunked and HTTP/2 requests that omit a Content-Length header, this calculation results in an empty body. As a consequence, WAF rules that inspect REQUEST_BODY, BODY_ARGS, ARGS_POST, JSON, or XML are skipped, allowing malicious payloads to bypass those checks. This flaw represents an insecure implementation (CWE-693) and permits attackers to evade payload inspections.

Affected Systems

Affected users are those running CrowdSec versions 1.5.0 through 1.7.7 inclusive. Version 1.7.8 and later incorporate the fix, restoring normal request body handling.

Risk and Exploitability

The CVSS score of 7.2 indicates a high severity, though the EPSS score of less than 1% implies a low probability of exploitation in practice, and the vulnerability is not listed in the CISA KEV catalog. Attackers can exploit the flaw by crafting HTTP/1.1 requests with Transfer-Encoding: chunked or HTTP/2 requests without a content‑length header, thereby manipulating CrowdSec into ignoring request body‑based rules. No privilege escalation or remote code execution is required; the risk is primarily a bypass of existing security checks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy CrowdSec version 1.7.8 or later to restore correct request body handling
  • Re‑evaluate and, if necessary, modify WAF rule sets to avoid dependence on request body content for critical detections
  • Implement monitoring to detect any unexpected changes in request body handling or rule bypass activity

Generated by OpenCVE AI on July 31, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-rw47-hm26-6wr7 CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests
History
Type Values Removed Values Added
First Time appeared Crowdsecurity
Crowdsecurity crowdsec
Vendors & Products Crowdsecurity
Crowdsecurity crowdsec
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description CrowdSec offers crowdsourced protection against malicious IPs. From 1.5.0 until 1.7.8, pkg/appsec/request.go NewParsedRequestFromRequest allocated a request body buffer from max(r.ContentLength, 0), so HTTP/1.1 requests using Transfer-Encoding: chunked and HTTP/2 requests without a content-length header produced an empty body and caused WAF rules targeting REQUEST_BODY, BODY_ARGS, ARGS_POST, JSON, or XML to be skipped. This issue is fixed in version 1.7.8.
Title CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests
Weaknesses CWE-693
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-693

    Protection Mechanism Failure

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 3:01 PM
Reserved
May 8, 2026, 4:23 PM
Status
Deferred
Published
Jul 16, 2026, 8:16 PM
Modified
Oct 24, 2026, 8:10 PM