Monoceros before 0.30 can exhaust memory via Content-Length
A request that declares a large Content-Length can kill a Monoceros worker by exhausting memory.
40
CVE-2026-115864
Memory-exhaustion DoS in Monoceros for Perl before 0.30
- CVSS
- —
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Monoceros before 0.30 for Perl reads a request body by asking sysread for the entire remaining declared Content-Length at once. Perl grows that buffer before any data arrives, so an oversized length exhausts memory and kills the worker with an uncatchable out-of-memory error before the application runs. A remote attacker can force a worker restart with each request of only a few bytes. Deployments on those versions are affected.
What to do: Upgrade Monoceros for Perl to version 0.30.
| Product | Affected | Fixed in |
|---|---|---|
| Monoceros | before 0.30 | 0.30 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Monoceros versions before 0.30 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory. The request body is read in a loop that asks sysread for all of the remaining declared length at once. Perl grows the read buffer to that size before any data arrives, so a length larger than available memory makes the worker exit with an uncatchable out of memory error before the application is called. A remote attacker can force a worker restart with each request of a few bytes.
- Weakness
- CWE-789