CVE-2026-116132

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk. The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it. A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk. The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it. A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

These are all security issues fixed in the perl-HTTP-Body-1.240.0-1.1 package on the GA media of openSUSE Tumbleweed.