# CVE-2026-115824

> As of 2026-10-25, CVE-2026-115824 is a vulnerability, EPSS 0.3% (25.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-115824 as of 2026-10-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-25

## What is CVE-2026-115824?

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.

The record classifies CVE-2026-115824 under weakness class [CWE-770](https://intel.threadlinqs.com/cwe/CWE-770). The identifier was first published 25 days ago.

## Severity and exploitation probability

- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 25.8% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-25

## Is CVE-2026-115824 being exploited?

It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.

## Affected products and versions

No affected-product or package list has been recorded for CVE-2026-115824 in the tracked sources. The vendor advisory and the references below are the authoritative statement of what is affected.

## How to fix CVE-2026-115824

Patch reference: [https://github.com/miyagawa/Starman/commit/d789a02dbe5408ef5f7a4659078d0008dd84c308.patch](https://github.com/miyagawa/Starman/commit/d789a02dbe5408ef5f7a4659078d0008dd84c308.patch). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-115824

No threat campaign in the Threadlinqs corpus currently references CVE-2026-115824, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, GitHub Security Advisories, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/miyagawa/Starman/commit/d789a02dbe5408ef5f7a4659078d0008dd84c308.patch)
- [github.com — patch (0f33f9b132b5e410d6cce722ff71988e22476acf)](https://github.com/miyagawa/Starman/commit/0f33f9b132b5e410d6cce722ff71988e22476acf.patch)
- [metacpan.org — release notes](https://metacpan.org/release/MIYAGAWA/Starman-0.4019/changes)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-115824
No Threadlinqs detection currently covers CVE-2026-115824; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
