Vulnerability in github.com/crowdsecurity/crowdsec (CVE-2026-44982)
Summary
Vulnerability in github.com/crowdsecurity/crowdsec (CVE-2026-44982). Risk of unauthorized operations or information disclosure. Exploitable via REQUEST_BODY. Mitigation: upgrade to 1.7.8 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44982 has been found in github.com/crowdsecurity/crowdsec.
Attackers can target a specific entry point like REQUEST_BODY over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade github.com/crowdsecurity/crowdsec to 1.7.8 or later.
If unsure, ask your IT team or search "github.com/crowdsecurity/crowdsec CVE-2026-44982" on the vendor's site.
CVE-2026-44982 (github.com/crowdsecurity/crowdsec) — CWE-693 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: REQUEST_BODY / BODY_ARGS / ARGS_POST / JSON
Patched: 1.7.8 — apply immediately
Workaround: No complete workaround is available.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-693) exists in github.com/crowdsecurity/crowdsec. Attackers reach the vulnerable code path via REQUEST_BODY without authentication.
Check the vendor advisory for the affected versions of github.com/crowdsecurity/crowdsec. Attack surface: REQUEST_BODY / BODY_ARGS / ARGS_POST / JSON.
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.
Update to 1.7.8.
Workaround: No complete workaround is available.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/crowdsecurity/crowdsec' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/crowdsecurity/crowdsec' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/crowdsecurity/crowdsecを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No complete workaround is available.パッチが適用されるまでの応急処置として、No complete workaround is available. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/crowdsecurity/crowdsec to 1.7.8ステージング環境で 1.7.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-44982 crowdsec
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com