CVE-2026-115825: Plack (Perl module) · Excessive Memory Allocation
Affects Plack (Perl module)Source CVE Database V5
Not known to be exploited : upgrade to 1.0056 soon.
Data as of 25 Oct 2026, 17:13 UTC
Rated High by the CNA (CPANSec) · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.0056
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Upgrade Plack (Perl module) to 1.0056.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CPANPlackpkg:cpan/PlackOther 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 protective measures such as limiting accepted Content-Length sizes at a reverse proxy or firewall to prevent excessively large allocations.
Description
HTTP::Server::PSGI versions before 1.0056 for Perl contain a vulnerability where a remote attacker can crash the server by sending a request with a large Content-Length header. The server attempts to allocate memory based on the declared Content-Length before reading the body, leading to an out-of-memory error and server crash. Since HTTP::Server::PSGI runs as a single process, the server remains down until manually restarted.