← back

CVE-2026-40561

hype MOSTLY HYPE · 18 hack

Legitimate vuln but zero active signal; pure automated disclosure chatter today.

What: HTTP Request Smuggling in Starlet (Perl web server) through v0.31 via improper header precedence—Content-Length prioritized over Transfer-Encoding in violation of RFC 7230, enabling request smuggling via reverse proxies.

Why it matters: Published today with no CVSS/EPSS scores, no KEV listing, and no public PoC or vendor advisory detected. Social signal is purely automated feed republication from NVD/CVE databases. No defender triage or patch activity reported.

Where it's seen: Five low-engagement posts, all feed-driven mirrors (CVEnew, Vulmon, Bluesky aggregators). No researcher analysis, no vendor statement, no exploitation chatter.

RISK: MODERATE — HTTP smuggling is a class attack; exposure depends on Starlet adoption and proxy configurations.

Generated by claude-haiku-4-5 from public posts and authoritative metadata. AI can make mistakes — verify against vendor advisories before acting. 5/3/2026, 4:35:39 AM

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.

Articles & coverage 14 articles

Page 1 of 3
NVD details 1 CWE ·0 vendors · 2 refs expand

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.

Weaknesses

References

Top posts driving the trend