Categories
CVE-2026-44981

Vulnerability in github.com/crowdsecurity/crowdsec (CVE-2026-44981)

Summary

Vulnerability in github.com/crowdsecurity/crowdsec (CVE-2026-44981). Risk of unauthorized operations or information disclosure. Exploitable via DefaultDecompressHandle. 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.7.0 until 1.7.8, the LAPI router used gin-contrib/gzip with DefaultDecompressHandle globally in pkg/apiserver/controllers/controller.go, causing /v1/watchers and /v1/watchers/login to decompress unauthenticated gzip-compressed JSON request bodies without enforcing a maximum decompressed size and allowing excessive heap allocation that can make LAPI unreachable. 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-44981 has been found in github.com/crowdsecurity/crowdsec.
Attackers can target a specific entry point like DefaultDecompressHandle over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
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-44981" on the vendor's site.

CVE-2026-44981 (github.com/crowdsecurity/crowdsec) — CWE-409
Attack surface: DefaultDecompressHandle
Patched: 1.7.8 — apply immediately
Workaround: If the LAPI is exposed on the network (either directly or through a reverse proxy), for example in the case of a multi-server deployment, restrict access to trusted IP addresses.
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.

❓ What is the problem

A vulnerability (CWE-409) exists in github.com/crowdsecurity/crowdsec. Attackers reach the vulnerable code path via DefaultDecompressHandle.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/crowdsecurity/crowdsec. Attack surface: DefaultDecompressHandle.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.8.

🛡️ Workaround

Workaround: If the LAPI is exposed on the network (either directly or through a reverse proxy), for example in the case of a multi-server deployment, restrict access to trusted IP addresses.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    If the LAPI is exposed on the network (either directly or through a reverse proxy), for example in the case of a multi-server deployment, restrict access to trusted IP addresses.

    パッチが適用されるまでの応急処置として、If the LAPI is exposed on the network (either directly or through a reverse proxy), for example in the case of a multi-server deployment, restrict access to trusted IP addresses. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade github.com/crowdsecurity/crowdsec to 1.7.8

    ステージング環境で 1.7.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/crowdsecurity/crowdsec
[{"type":"SEMVER","events":[{"introduced":"1.7.0"},{"fixed":"1.7.8"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details