Skip to main content
VulnerabilityPublished Updated

CVE-2026-116127: Starlet versions before 0.33 for Perl send a body in responses to HEAD requests, corrupting the next

Affects starletSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116127· Medium

Not known to be exploited.

Data as of 5 Nov 2026, 12:35 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10starletpkg:deb/ubuntu/starlet?arch=source&distro=stonkingOther threatsAffected
  • =0.31-2build1
  • =0.31-3
  • =0.32-1
Fixed in–
Ubuntu 26.04 LTSstarletpkg:deb/ubuntu/starlet?arch=source&distro=resoluteOther threatsAffected
  • =0.31-2
  • =0.31-2build1
Fixed in–
Ubuntu 24.04 LTSstarletpkg:deb/ubuntu/starlet?arch=source&distro=nobleOther threatsAffected
  • =0.31-2
Fixed in–
Ubuntu 22.04 LTSstarletpkg:deb/ubuntu/starlet?arch=source&distro=jammyOther threatsAffected
  • =0.31-1.1
Fixed in–
Ubuntu 20.04 LTSstarletpkg:deb/ubuntu/starlet?arch=source&distro=focalOther threatsAffected
  • =0.31-1
Fixed in–
Ubuntu 18.04 LTSstarletpkg:deb/ubuntu/starlet?arch=source&distro=bionicOther threatsAffected
  • =0.31-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…