CVE-2026-44982

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.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.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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
47(Track)
EG Risk 47/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
Severity72% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 17, 2026

Advisory Details (5)

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

CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests · Advisory · crowdsecurity/crowdsec · GitHub

https://github.com/crowdsecurity/crowdsec/security/advisories/GHSA-rw47-hm26-6wr7
github_release Patch Available

v1.7.8

Patch available: crowdsecurity/crowdsec v1.7.8

https://github.com/crowdsecurity/crowdsec/releases/tag/v1.7.8
github_pr

WAF: enforce body size limitation

Fix merged in crowdsecurity/crowdsec PR #4355 on 2026-04-28 — awaiting tagged release

https://github.com/crowdsecurity/crowdsec/pull/4355
github_commit

commit 57a793548671 (crowdsecurity/crowdsec)

Fix landed in crowdsecurity/crowdsec commit 57a793548671 — awaiting tagged release

https://github.com/crowdsecurity/crowdsec/commit/57a793548671e6bbd2cde5562fe87b856ec9c642
github_commit

commit 3d5c4d9b1270 (crowdsecurity/crowdsec)

Fix landed in crowdsecurity/crowdsec commit 3d5c4d9b1270 — awaiting tagged release

https://github.com/crowdsecurity/crowdsec/commit/3d5c4d9b127091e9063b9b5eb785372a599a4435

Vendor 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)
PackageVulnerable rangeFixed inDependents
github.com/crowdsecurity/crowdsec1.7.8

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 14× 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-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 10:02 UTCEG score recompute
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:17 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:15 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:24 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-13 23:00 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-05-27 20:35 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44982?
CVE-2026-44982 is a high vulnerability published on May 27, 2026. 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…
When was CVE-2026-44982 disclosed?
CVE-2026-44982 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-44982 actively exploited?
CVE-2026-44982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44982?
CVE-2026-44982 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-44982?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44982, 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-44982

Explore →

Is Your Infrastructure Affected by CVE-2026-44982?

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