CVE-2026-116127
Starlet versions before 0.33 for Perl send a body in responses to HEAD requests, corrupting the next response on a persistent or pipelined connection. The request method is not passed to the response writer, so whatever body the application returns for a HEAD request is sent. With Plack::Middleware::Head the body is empty, but an HTTP/1.1 response without a Content-Length header still gets the chunked encoding terminator. Responses with status 204 or 304 are also sent with their body. Pipelined GET and HEAD requests keep the connection open even when keep-alive is disabled, which is the default. A client or proxy reading the connection takes the extra bytes as the start of the next response, which may desynchronize a proxy that shares the connection across clients.
- Score
- –
- Published
- 2026-10-30
- Links
- NVD · cve.org · Report wrong data
Matched ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| www/p5-Starlet | p5-Starlet | 0.32 | unaddressed | perl@FreeBSD.org |
Template for a VuXML entry
Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.
Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.
www/p5-Starlet (CPE matched by the package name) has no USES=cpe. The CVE was matched through a CPE from another source, so the package and the version range may belong to a different product. Check the CVE record before using this entry.
<vuln vid="FIXME (make newentry)">
<topic>p5-Starlet -- FIXME</topic>
<affects>
<package>
<name>p5-Starlet</name>
<range><lt>0.33</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CVE-2026-116127: Starlet versions before 0.33 for Perl send a body in
responses to HEAD requests, corrupting the next response on a
persistent or pipelined connection. The request method is not
passed to the response writer, so whatever body the application
returns for a HEAD request is sent. With Plack::Middleware::Head
the body is empty, but an HTTP/1.1 response without a Content-
Length header still gets the chunked encoding terminator. Responses
with status 204 or 304 are also sent with their body. Pipelined GET
and HEAD requests keep the connection open even when keep-alive is
disabled, which is the default. A client or proxy reading the
connection takes the extra bytes as the start of the next response,
which may desynchronize a proxy that shares the connection across
clients.</p>
</body>
</description>
<references>
<cvename>CVE-2026-116127</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-116127</url>
</references>
<dates>
<discovery>2026-10-30</discovery>
<entry>2026-10-30</entry>
</dates>
</vuln>