CVE-2026-115864: Monoceros versions before 0.30 for Perl allow a request declaring a large Content-Length to kill a
Source GCVE Database
Not known to be exploited : upgrade to 0.30 soon.
Data as of 10 Nov 2026, 01:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 0.30
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Monoceros (Perl module) to 0.30.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Monoceros | Affected
| Fixed in
|
CPANMonocerospkg:cpan/MonocerosOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, consider implementing request size limits or filtering to mitigate large Content-Length headers at a network or proxy level.
Description
Monoceros versions before 0.30 for Perl contain a vulnerability where a remote attacker can send a request with a large Content-Length header to exhaust memory and kill a worker process. This occurs because the request body is read in a loop that attempts to allocate a buffer equal to the declared Content-Length before any data arrives, causing an uncatchable out-of-memory error and worker termination.