Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters
What fixes it
- 0.035CVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Reports 4
3 outlets mention it. Reports are not confirmation; each links to its source.
- 🚨 CVE-2026-114629 Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters. Web::Dispatch::ParamParser::get_unpacked_body_from reaTelegram: CVE Notify, 24 Oct 2026
- 🚨 CVE-2026-114629 Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters. Web::Dispatch::ParamParser::get_unpacked_body_from reaTelegram: CVE Notify, 24 Oct 2026
- @infosec.skyfleet.blue: CVE-2026-114629: Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parametersBluesky: CVE posts, 24 Oct 2026
- CVE-2026-114629: Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parametersoss-security, 24 Oct 2026
Description
Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters.
Web::Dispatch::ParamParser::get_unpacked_body_from reads an application/x-www-form-urlencoded body using a single read call, with no cap and the return value ignored. Perl's read grows the buffer to the requested length before reading, so the declared Content-Length determines the allocation.
An attacker can trigger this through any route whose dispatch specification has a % body-parameter match, such as sub (POST + %name=), sending a Content-Length far larger than the body actually sent. No authentication is involved.
Text from CVE List
Affected versions 1
- Productaffected: all versions before 0.035CVE List