How severe is GHSA-273h-gvwr-c3qj?

No CVSS score has been assigned to GHSA-273h-gvwr-c3qj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-273h-gvwr-c3qj?

GHSA-273h-gvwr-c3qj affects the following packages: github.com/crowdsecurity/crowdsec (Go). Ecosystems affected: Go.

How do I fix GHSA-273h-gvwr-c3qj?

Update github.com/crowdsecurity/crowdsec to 1.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-273h-gvwr-c3qj is resolved across your whole dependency graph.

How do I detect GHSA-273h-gvwr-c3qj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crowdsecurity/crowdsec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-273h-gvwr-c3qj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-273h-gvwr-c3qj actively exploited in the wild?

No public exploit code has been indexed for GHSA-273h-gvwr-c3qj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-273h-gvwr-c3qj?

GHSA-273h-gvwr-c3qj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-273h-gvwr-c3qj?

GHSA-273h-gvwr-c3qj is classified as CWE-409 (CWE-409). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-273h-gvwr-c3qj published, and has it been updated?

GHSA-273h-gvwr-c3qj was published on May 27, 2026 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CrowdSec LAPI: Denial of Service via Unbounded Gzip DecompressionGHSA-273h-gvwr-c3qj

GHSA-273h-gvwr-c3qj is a CWE-409 vulnerability in github.com/crowdsecurity/crowdsec. A fix is available for github.com/crowdsecurity/crowdsec — see the affected versions and patch details below.

Also known asCVE-2026-44981GO-2026-5041

Published

May 27, 2026

Updated

Jun 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-273h-gvwr-c3qj.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/crowdsecurity/crowdsec

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The LAPI router uses gin-contrib/gzip with DefaultDecompressHandle globally (pkg/apiserver/controllers/controller.go). This middleware decompresses incoming request bodies without enforcing a maximum decompressed size.

The endpoints /v1/watchers or /v1/watchers/login require no authentication. An attacker can send small gzip-compressed JSON payloads that, when decompressed, result in hundreds of MB of valid JSON occupying server memory. Sending enough requests concurrently will cause LAPI to allocate excessive heap memory, leading the OS to forcibly terminate the process.

This vulnerability is not exploitable from the network in default configurations, as LAPI only listens on the loopback interface. If developers' applications are using a multi-server setup, LAPI will be exposed in the network, in which case they are at risk if untrusted IPs can access it.

Impact

Exploiting this vulnerability will make LAPI unreachable, meaning that bouncers will not be able to fetch new decisions (but existing decisions will still be enforced) and log processors will not be able to send alerts, effectively denying the creation of new decisions.

Workarounds

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/crowdsecurity/crowdsec`	≥ 1.7.0&&< 1.7.8	1.7.8`go get github.com/crowdsecurity/crowdsec@v1.7.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crowdsecurity/crowdsec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/crowdsecurity/crowdsec to 1.7.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-273h-gvwr-c3qj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The LAPI router uses `gin-contrib/gzip` with `DefaultDecompressHandle` globally (`pkg/apiserver/controllers/controller.go`). This middleware decompresses incoming request bodies without enforcing a maximum decompressed size. The endpoints `/v1/watchers` or `/v1/watchers/login` require no authentication. An attacker can send small gzip-compressed JSON payloads that, when decompressed, result in hundreds of MB of valid JSON occupying server memory. Sending enough requests concurrently will cause LAPI to allocate excessive heap memory, leading the OS to forcibly terminate the process. This vu

O3 Security · Impact-Aware SCA

Is GHSA-273h-gvwr-c3qj in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CrowdSec LAPI: Denial of Service via Unbounded Gzip DecompressionGHSA-273h-gvwr-c3qj

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-273h-gvwr-c3qj in your dependencies?