cve.bz

CVE-2026-115824

7.5 highEPSS 0.6%

High (7.5). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies. The chunked body decoder keeps each chunk in memory until the whole chunk and its CRLF have arrived, and sets no limit on the length of a chunk-size line. A client that declares a huge chunk size and streams data, or sends a chunk-size line that never ends, grows the buffer for as long as it keeps sending. A remote attacker can exhaust worker memory with a single connection.

Severity

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.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-115824 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115824?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115824?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-115824 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13starmanno fix listedDEBIAN-CVE-2026-115824
Debian14starman0.4019-1DEBIAN-CVE-2026-115824
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morestarmanno fix listedUBUNTU-CVE-2026-115824
openSUSETumbleweedperl-Starman0.4019-1.1openSUSE-SU-2026:12276-1

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

Red Hat

Red Hat rates this Important.

Red Hat's statement

Starman before 0.4019 buffers each chunked request-body chunk entirely in memory (with no bound on the chunk-size line length) before the terminating CRLF arrives. A remote, unauthenticated client can declare a huge chunk size and stream data, or send a never-ending chunk-size line, causing the worker process's memory to grow without bound (an 80 MiB request pushed a worker to ~900 MB RSS pre-fix), resulting in denial of service. Red Hat products do not ship Starman; the component appears only in Fedora community channels (perl-Starman 0.4018), which are below the fixed version 0.4019 that streams chunked bodies to Plack::TempBuffer.

Red Hat's mitigation

Upgrade to Starman 0.4019 or later, which streams chunked request bodies to the temporary buffer (spilling to disk) instead of holding whole chunks in memory and bounds chunk-size line parsing. Until then, front Starman with a reverse proxy that limits request-body size and chunked-encoding line lengths, or reject/limit chunked transfer-encoded requests at the proxy.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115824.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON