CVE-2026-44982: Github.com/crowdsecurity/crowdsec CrowdSec AppSec Silently Drops Request Vulnerability

HIGH
Advisory Identifier: GHSA-rw47-hm26-6wr7
CVSS 7.2
CWE-693
Published
Advisory Summary

CVE-2026-44982 is a HIGH (CVSS 7.2) crowdsec appsec silently drops request vulnerability (CWE-693: Protection Mechanism Failure) affecting Github.com/crowdsecurity/crowdsec libraries in the Go ecosystem. The issue involves crowdsec appsec silently drops request body for chunked / http-2 requests. Remediation is available by upgrading affected packages to version 1.7.8.

CVE-2026-44982 at a Glance

CVE Identifier CVE-2026-44982
GHSA Identifier GHSA-rw47-hm26-6wr7
Severity HIGH
CVSS v3.1 Base Score 7.2
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product Github.com/crowdsecurity/crowdsec
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-44982

To remediate this vulnerability, upgrade all affected Github.com/crowdsecurity/crowdsec dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/crowdsecurity/crowdsec fixed: 1.7.8
Upgrade github.com/crowdsecurity/crowdsec to 1.7.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/crowdsecurity/crowdsec

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44982, inspect your project dependencies for Github.com/crowdsecurity/crowdsec:

inspect dependencies for github.com/crowdsecurity/crowdsec

Analyze the terminal output to locate any version of Github.com/crowdsecurity/crowdsec in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In Github.com/crowdsecurity/crowdsec, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The CrowdSec AppSec component fails to read the HTTP request body for any request whose `Content-Length` is not positive — most notably HTTP/1.1 requests using `Transfer-Encoding: chunked` and HTTP/2 requests sent without a `content-length` header. Coraza is then evaluated against an empty body, so every WAF rule targeting `REQUEST_BODY`, `BODY_ARGS`, `ARGS_POST`, `JSON`, or `XML` silently fails to match. An unauthenticated remote attacker can bypass the entire AppSec body-inspection pipeline by changing a single framing header on an otherwise-malicious request. The bypassed request is forwarded as `allow` and produces no WAF log entry. ## Affected versions - `github.com/crowdsecurity/crowdsec` — all releases up to and including **v1.7.7**. ## Affected component `pkg/appsec/request.go`, function `NewParsedRequestFromRequest`. ## Root cause ```go func NewParsedRequestFromRequest(r *http.Request, logger *log.Entry) (ParsedRequest, error) { var err error contentLength := max(r.ContentLength, 0) body := make([]byte, contentLength) if r.Body != nil { _, err = io.ReadFull(r.Body, body) if err != nil { return ParsedRequest{}, fmt.Errorf("unable to read body: %s", err) } r.Body = io.NopCloser(bytes.NewBuffer(body)) } ... } ``` Go's `net/http` server sets `r.ContentLength = -1` when the request uses `Transfer-Encoding: chunked` with no `Content-Length` header, or when an HTTP/2 request omits the `content-length` pseudo-header (DATA-frame-only body). With `ContentLength == -1`: 1. `max(-1, 0)` evaluates to `0`. 2. `make([]byte, 0)` allocates a zero-length slice. 3. `io.ReadFull` on a zero-length buffer needs zero bytes and returns immediately without touching `r.Body`. 4. The empty buffer is written back onto the request and onto the cloned request constructed later in the same function. Every downstream consumer then sees an empty body. In the AppSec runner, `WriteRequestBody` is skipped because the parsed body has zero length, and `ProcessRequestBody` runs against nothing. ## Impact Every body-scanning rule is bypassed for any request whose framing makes `Content-Length` non-positive. In default CrowdSec deployments using the standard AppSec collections, the bypass affects any rule with `zones` containing `BODY_ARGS`, `JSON`, `XML`, `REQUEST_BODY`, or `ARGS_POST`. No configuration option mitigates the issue — the defect is in the request parser, not in any ruleset. Bypassed requests do not produce a WAF log entry, so operators have no signal that rules are being skipped. Header-only and URI-only rules are unaffected. ## Workarounds No complete workaround is available.

CVE-2026-44982 Affected Github.com/crowdsecurity/crowdsec Versions

1 component(s)
Fixed Versions:
1.7.8
Product / Package Ecosystem Affected Versions Fixed Version
github.com/crowdsecurity/crowdsec
Go
≥ 1.5.0
< 1.7.8
1.7.8

References

Frequently Asked Questions

What is CVE-2026-44982?
CVE-2026-44982 is a security vulnerability in Github.com/crowdsecurity/crowdsec involving CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests under CWE-693: Protection Mechanism Failure.
Which Github.com/crowdsecurity/crowdsec versions are affected?
Affected versions include releases prior to 1.7.8 across affected packages: github.com/crowdsecurity/crowdsec.
What version fixes CVE-2026-44982?
Upgrading to 1.7.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/crowdsecurity/crowdsec affected?
Yes, github.com/crowdsecurity/crowdsec is affected in releases prior to 1.7.8. Upgrade your dependency to 1.7.8 or later.
What is the CVSS score of CVE-2026-44982?
CVE-2026-44982 has a CVSS v3.1 base score of 7.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-44982?
CVE-2026-44982 is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check Go dependencies for CVE-2026-44982?
Run the dependency tree command: 'inspect dependencies for github.com/crowdsecurity/crowdsec'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rw47-hm26-6wr7",
  "modified" : "2026-05-27T19:58:15Z",
  "published" : "2026-05-27T19:58:15Z",
  "aliases" : [ "CVE-2026-44982" ],
  "summary" : "CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests",
  "details" : "## Summary\n\nThe CrowdSec AppSec component fails to read the HTTP request body for any request whose `Content-Length` is not positive — most notably HTTP/1.1 requests using `Transfer-Encoding: chunked` and HTTP/2 requests sent without a `content-length` header. Coraza is then evaluated against an empty body, so every WAF rule targeting `REQUEST_BODY`, `BODY_ARGS`, `ARGS_POST`, `JSON`, or `XML` silently fails to match.\n\nAn unauthenticated remote attacker can bypass the entire AppSec body-inspection pipeline  by changing a single framing header on an otherwise-malicious request. The bypassed request is forwarded as `allow` and produces no WAF log entry.\n\n## Affected versions\n\n- `github.com/crowdsecurity/crowdsec` — all releases up to and including **v1.7.7**.\n\n## Affected component\n\n`pkg/appsec/request.go`, function `NewParsedRequestFromRequest`.\n\n## Root cause\n\n```go\nfunc NewParsedRequestFromRequest(r *http.Request, logger *log.Entry) (ParsedRequest, error) {\n    var err error\n    contentLength := max(r.ContentLength, 0)\n    body := make([]byte, contentLength)\n    if r.Body != nil {\n        _, err = io.ReadFull(r.Body, body)\n        if err != nil {\n            return ParsedRequest{}, fmt.Errorf(\"unable to read body: %s\", err)\n        }\n        r.Body = io.NopCloser(bytes.NewBuffer(body))\n    }\n    ...\n}\n```\n\nGo's `net/http` server sets `r.ContentLength = -1` when the request uses `Transfer-Encoding: chunked` with no `Content-Length` header, or when an HTTP/2 request omits the `content-length` pseudo-header (DATA-frame-only body). With `ContentLength == -1`:\n\n1. `max(-1, 0)` evaluates to `0`.\n2. `make([]byte, 0)` allocates a zero-length slice.\n3. `io.ReadFull` on a zero-length buffer needs zero bytes and returns immediately without touching `r.Body`.\n4. The empty buffer is written back onto the request and onto the cloned request constructed later in the same function.\n\nEvery downstream consumer then sees an empty body. In the AppSec runner, `WriteRequestBody` is skipped because the parsed body has zero length, and `ProcessRequestBody` runs against nothing.\n\n## Impact\n\nEvery body-scanning rule is bypassed for any request whose framing makes `Content-Length` non-positive. In default CrowdSec deployments using the standard AppSec collections, the bypass affects any rule with `zones` containing `BODY_ARGS`, `JSON`, `XML`, `REQUEST_BODY`, or `ARGS_POST`.\n\nNo configuration option mitigates the issue — the defect is in the request parser, not in any ruleset. Bypassed requests do not produce a WAF log entry, so operators have no signal that rules are being skipped.\n\nHeader-only and URI-only rules are unaffected.\n\n## Workarounds\n\nNo complete workaround is available.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/crowdsecurity/crowdsec"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.5.0"
      }, {
        "fixed" : "1.7.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.7.7"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-rw47-hm26-6wr7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/crowdsecurity/crowdsec"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-27T19:58:15Z",
    "nvd_published_at" : null
  }
}