Security Advisories (1)
CVE-2026-115825 (2026-10-25)

HTTP::Server::PSGI versions before 1.0056 for Perl allow a single request to crash the server by declaring a large Content-Length. The request body is read with sysread() calls sized by the remaining Content-Length. Perl grows the read buffer to the requested length before any data arrives, so the server tries to allocate as much memory as the client declares. A remote attacker can send one request with a large Content-Length and a few body bytes, and perl exits with an out-of-memory error before the application is called. HTTP::Server::PSGI runs as a single process, so the server stays down until restarted.

NAME

Plack::App::PSGIBin - Run .psgi files from a directory

SYNOPSIS

use Plack::App::PSGIBin;
use Plack::Builder;

my $app = Plack::App::PSGIBin->new(root => "/path/to/psgi/scripts")->to_app;
builder {
    mount "/psgi" => $app;
};

# Or from the command line
plackup -MPlack::App::PSGIBin -e 'Plack::App::PSGIBin->new(root => "/path/psgi/scripts")->to_app'

DESCRIPTION

This application loads .psgi files (or actually whichever filename extensions) from the root directory and run it as a PSGI application. Suppose you have a directory containing foo.psgi and bar.psgi, map this application to /app with Plack::App::URLMap and you can access them via the URL:

http://example.com/app/foo.psgi
http://example.com/app/bar.psgi

to load them. You can rename the file to the one without .psgi extension to make the URL look nicer, or use the URL rewriting tools like Plack::Middleware::Rewrite to do the same thing.

AUTHOR

Tatsuhiko Miyagawa

SEE ALSO

Plack::App::CGIBin