CVE-2026-44981

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 17, 2026

Advisory Details (3)

Auto-updated Jul 16, 2026
Patch available. Sources: github_commit, github.
github Patch Available

CrowdSec LAPI: Denial of Service via Unbounded Gzip Decompression · Advisory · crowdsecurity/crowdsec · GitHub

https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-273h-gvwr-c3qj
github_commit

commit 56d0d6915f7f (crowdsecurity/crowdsec)

Fix landed in crowdsecurity/crowdsec commit 56d0d6915f7f — awaiting tagged release

https://github.com/crowdsecurity/crowdsec/commit/56d0d6915f7f25941dc5b4f484028646f6601a37
github_commit

commit 54a0dfe6c16b (crowdsecurity/crowdsec)

Fix landed in crowdsecurity/crowdsec commit 54a0dfe6c16b — awaiting tagged release

https://github.com/crowdsecurity/crowdsec/commit/54a0dfe6c16b7687b0da6634e0b19ef0f5d9bb30

Vendor Advisories for CVE-2026-44981(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)
PackageVulnerable rangeFixed inDependents
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 5× in last 7d / 37× 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.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 05:11 UTCEG score recompute
  11. 2026-08-23 14:54 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 01:24 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 11:13 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 16:23 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:46 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 03:27 UTCEG score recompute
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 46 more
  1. 2026-08-14 01:24 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 15:46 UTCEG score recompute
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-12 02:33 UTCEG score recompute
  6. 2026-08-11 00:10 UTCEG score recompute
  7. 2026-08-11 00:00 UTCEPSS rescore
  8. 2026-08-09 21:38 UTCEG score recompute
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 02:15 UTCEG score recompute
  11. 2026-08-07 00:14 UTCEG score recompute
  12. 2026-08-06 13:46 UTCEPSS rescore
  13. 2026-08-05 20:51 UTCEG score recompute
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-04 15:10 UTCEPSS rescore
  16. 2026-08-04 10:38 UTCEPSS rescore
  17. 2026-08-03 16:25 UTCEG score recompute
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 04:09 UTCEG score recompute
  20. 2026-08-02 02:27 UTCEPSS rescore
  21. 2026-08-01 15:06 UTCEG score recompute
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-31 07:07 UTCEG score recompute
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-29 14:45 UTCEG score recompute
  27. 2026-07-28 15:36 UTCEPSS rescore
  28. 2026-07-27 14:13 UTCEPSS rescore
  29. 2026-07-27 10:02 UTCEG score recompute
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-24 14:17 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 03:15 UTCEG score recompute
  36. 2026-07-22 14:08 UTCEPSS rescore
  37. 2026-07-20 17:08 UTCEPSS rescore
  38. 2026-07-19 14:31 UTCEPSS rescore
  39. 2026-07-19 02:29 UTCEPSS rescore
  40. 2026-07-18 10:04 UTCEPSS rescore
  41. 2026-07-16 20:10 UTCEG score recompute▲ 8.20
  42. 2026-07-16 20:09 UTCMITRE cvelistV5CVSS v3 → 8.2 · CVSS v4 → 8.2 · severity → HIGH
  43. 2026-06-14 23:18 UTCEPSS rescore
  44. 2026-06-13 23:00 UTCEPSS rescore
  45. 2026-06-12 23:12 UTCEPSS rescore
  46. 2026-05-27 20:35 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44981?
CVE-2026-44981 is a high vulnerability published on May 27, 2026. 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…
When was CVE-2026-44981 disclosed?
CVE-2026-44981 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44981 actively exploited?
CVE-2026-44981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44981?
CVE-2026-44981 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-44981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44981, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44981

Explore →

Is Your Infrastructure Affected by CVE-2026-44981?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs