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.
CVE-2026-44982
This high-severity CVE scores 7.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(low)
- EG Risk
- —
- EPSS
- 12.2%
- KEV
- Not listed
Published
May 27, 2026
Last Modified
July 17, 2026
Advisory Details (5)
Auto-updated Jul 16, 2026CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests · Advisory · crowdsecurity/crowdsec · GitHub
https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-rw47-hm26-6wr7v1.7.8
Patch available: crowdsecurity/crowdsec v1.7.8
https://github.com/crowdsecurity/crowdsec/releases/tag/v1.7.8WAF: enforce body size limitation
Fix merged in crowdsecurity/crowdsec PR #4355 on 2026-04-28 — awaiting tagged release
https://github.com/crowdsecurity/crowdsec/pull/4355commit 57a793548671 (crowdsecurity/crowdsec)
Fix landed in crowdsecurity/crowdsec commit 57a793548671 — awaiting tagged release
https://github.com/crowdsecurity/crowdsec/commit/57a793548671e6bbd2cde5562fe87b856ec9c642commit 3d5c4d9b1270 (crowdsecurity/crowdsec)
Fix landed in crowdsecurity/crowdsec commit 3d5c4d9b1270 — awaiting tagged release
https://github.com/crowdsecurity/crowdsec/commit/3d5c4d9b127091e9063b9b5eb785372a599a4435Vendor Advisories for CVE-2026-44982(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/crowdsecurity/crowdsec | — | 1.7.8 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-27 20:35 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS 91%CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS 99%CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8MEDIUM
- CVE-2020-10887EG 9.8EPSS 90%CRITICAL
- CVE-2017-3197EG 9.8EPSS 92%CRITICAL
- CVE-2018-9318EG 9.8EPSS 90%CRITICAL
- CVE-2018-9311EG 9.8EPSS 90%CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2022-22759EG 9.6CRITICAL
Frequently asked(5)
What is CVE-2026-44982?
When was CVE-2026-44982 disclosed?
Is CVE-2026-44982 actively exploited?
What is the CVSS score of CVE-2026-44982?
How do I remediate CVE-2026-44982?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44982
Is Your Infrastructure Affected by CVE-2026-44982?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.