cve.bz

CVE-2026-115864 Monoceros versions before 0.30 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory

7.5 highEPSS 0.6%

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

On this page
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.

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% estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-13. 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-11-12. 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-789 Memory Allocation with Excessive Size Value
Published
Modified
Assigned by
CPANSec (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

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

Badge for a README or a site

CVE-2026-115864

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-115864](https://cve.bz/cve/badge/CVE-2026-115864.svg)](https://cve.bz/cve/CVE-2026-115864)

HTML:

<a href="https://cve.bz/cve/CVE-2026-115864"><img src="https://cve.bz/cve/badge/CVE-2026-115864.svg" alt="CVE-2026-115864"></a>

Versions

From the CNA's record in the CVE List.

ProductAffected
Monocerosbefore 0.30

History

  1. Scored 7.5 high
  2. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON