CVE-2026-40561: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in KAZUHO Starlet
Starlet versions through 0.31 for Perl allows HTTP Request Smuggling via Improper Header Precedence. Starlet incorrectly prioritizes "Content-Length" over "Transfer-Encoding: chunked" when both headers are present in an HTTP request. Per RFC 7230 3.3.3, Transfer-Encoding must take precedence. An attacker could exploit this to smuggle malicious HTTP requests via a front-end reverse proxy.
AI Analysis
Technical Summary
KAZUHO Starlet versions up to 0.31 for Perl contain an HTTP Request Smuggling vulnerability caused by inconsistent interpretation of HTTP headers. Specifically, the server incorrectly gives precedence to the Content-Length header over the Transfer-Encoding: chunked header when both are present in an HTTP request. According to RFC 7230 section 3.3.3, Transfer-Encoding must take precedence. This discrepancy can be exploited by attackers to smuggle unauthorized HTTP requests via a front-end reverse proxy, potentially bypassing security controls or causing request confusion.
Potential Impact
An attacker could exploit this vulnerability to perform HTTP Request Smuggling attacks, which may lead to unauthorized request injection or manipulation when the vulnerable Starlet server is used behind a reverse proxy. This can undermine the integrity of HTTP request handling and potentially allow bypassing of security mechanisms. However, no known exploits in the wild have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider deploying additional protections at the reverse proxy or web application firewall level to detect or block suspicious request patterns involving conflicting Content-Length and Transfer-Encoding headers.
CVE-2026-40561: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in KAZUHO Starlet
Description
Starlet versions through 0.31 for Perl allows HTTP Request Smuggling via Improper Header Precedence. Starlet incorrectly prioritizes "Content-Length" over "Transfer-Encoding: chunked" when both headers are present in an HTTP request. Per RFC 7230 3.3.3, Transfer-Encoding must take precedence. An attacker could exploit this to smuggle malicious HTTP requests via a front-end reverse proxy.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
KAZUHO Starlet versions up to 0.31 for Perl contain an HTTP Request Smuggling vulnerability caused by inconsistent interpretation of HTTP headers. Specifically, the server incorrectly gives precedence to the Content-Length header over the Transfer-Encoding: chunked header when both are present in an HTTP request. According to RFC 7230 section 3.3.3, Transfer-Encoding must take precedence. This discrepancy can be exploited by attackers to smuggle unauthorized HTTP requests via a front-end reverse proxy, potentially bypassing security controls or causing request confusion.
Potential Impact
An attacker could exploit this vulnerability to perform HTTP Request Smuggling attacks, which may lead to unauthorized request injection or manipulation when the vulnerable Starlet server is used behind a reverse proxy. This can undermine the integrity of HTTP request handling and potentially allow bypassing of security mechanisms. However, no known exploits in the wild have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider deploying additional protections at the reverse proxy or web application firewall level to detect or block suspicious request patterns involving conflicting Content-Length and Transfer-Encoding headers.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-04-14T11:35:53.644Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f6a35ccbff5d861079c762
Added to database: 5/3/2026, 1:22:36 AM
Last enriched: 5/3/2026, 1:36:18 AM
Last updated: 5/3/2026, 6:56:01 AM
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.