cve.bz

CVE-2026-7790 ninenines cowlib: Uncontrolled Resource Consumption

8.7 highEPSS 0.4%Fix available

High (8.7) in ninenines cowlib. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in cowlib 2.16.1.

On this page
Uncontrolled Resource Consumption vulnerability in ninenines cowlib (cow_http_te module) allows Excessive Allocation. The chunked transfer-encoding parser in cow_http_te accepts an unbounded number of hex digits in the chunk-size field. Each digit causes a bignum multiplication (Len * 16 + digit), so parsing N hex digits requires O(N²) CPU work and O(N) memory. Additionally, when input is drip-fed, the parser discards the accumulated length on each partial read and restarts from zero on resumption, raising the cost to O(N³). An unauthenticated remote attacker can exploit this by sending an HTTP/1.1 request with Transfer-Encoding: chunked and a very long chunk-size hex string to cause denial of service through CPU exhaustion and memory amplification. This vulnerability is associated with program file src/cow_http_te.erl and program routines cow_http_te:stream_chunked/2, cow_http_te:chunked_len/4. This issue affects cowlib: from 0.6.0 before 2.16.1.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-7790 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7790?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7790?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7790 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ninenines cowlibfrom 0.6.0 before 2.16.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-7790Hexcowlib>=0.6.0 <2.16.12.16.1
EEF-CVE-2026-77902.16.0, 2.15.0, 2.14.0, 2.13.0, 2.12.1 and 31 moreno fix published
GHSA-32p9-57cr-4x65Hexcowlib>=0.6.0 <2.16.12.16.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13erlang-cowlibno fix listedDEBIAN-CVE-2026-7790
Debian14erlang-cowlib2.17.1-1DEBIAN-CVE-2026-7790
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 5 moreerlang-cowlibno fix listedUBUNTU-CVE-2026-7790
Azure Linux3rabbitmq-server3.13.7-5AZL-86790

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON