cve.bz

CVE-2026-115823 HTTP Request Smuggling

9.1 criticalEPSS 0.4%

Critical (9.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections. For a HEAD request Starman omits chunked framing but still writes the body returned by the application, on both the array and streaming response paths. Responses with a 1xx, 204 or 304 status also carry the body. On a keep-alive or pipelined connection the client reads those bytes as the start of the next response. A front-end proxy that reuses upstream connections may then pair responses with the wrong requests.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

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

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13starmanno fix listedDEBIAN-CVE-2026-115823
Debian14starman0.4019-1DEBIAN-CVE-2026-115823
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morestarmanno fix listedUBUNTU-CVE-2026-115823
openSUSETumbleweedperl-Starman0.4019-1.1openSUSE-SU-2026:12276-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Starman, a PSGI/Plack web server for Perl. Starman versions before 0.4019 improperly send response bodies for HTTP responses that should contain headers only, such as HEAD requests and responses with 1xx, 204, or 304 status codes. On keep-alive or pipelined connections this desynchronizes HTTP responses: a client, or a front-end proxy that reuses upstream connections, may read those extra bytes as the start of the next response and pair responses with the wrong requests, resulting in information disclosure or request-response mispairing. This issue is fixed in Starman 0.4019.

Red Hat's mitigation

Upgrade to Starman 0.4019 or later. As a workaround, enable Plack::Middleware::Head, as suggested by the upstream CNA (CPANSec).

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115823.

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON