Security Advisories (10)
CPANSA-Mojolicious-2022-03 (2022-12-10)

Mojo::DOM did not correctly parse <script> tags.

CPANSA-Mojolicious-2021-02 (2021-06-01)

Small sessions could be used as part of a brute-force attack to decode the session secret.

CVE-2021-47208 (2021-03-16)

A bug in format detection can potentially be exploited for a DoS attack.

CPANSA-Mojolicious-2018-03 (2018-05-19)

Mojo::UserAgent was not checking peer SSL certificates by default.

CPANSA-Mojolicious-2018-02 (2018-05-11)

GET requests with embedded backslashes can be used to access local files on Windows hosts

CVE-2018-25100 (2018-02-13)

Mojo::UserAgent::CookieJar leaks old cookies because of the missing host_only flag on empty domain.

CPANSA-Mojolicious-2015-01 (2015-02-02)

Directory traversal on Windows

CPANSA-Mojolicious-2014-01 (2014-10-07)

Context sensitivity of method param could lead to parameter injection attacks.

CVE-2024-58134 (2025-05-03)

Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default. These predictable default secrets can be exploited by an attacker to forge session cookies.  An attacker who knows or guesses the secret could compute valid HMAC signatures for the session cookie, allowing them to tamper with or hijack another user’s session.

CVE-2026-14803 (2026-07-06)

Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder. The pure-Perl decode path (`_decode_value` dispatching to `_decode_array` and `_decode_object`) recurses with no depth limit, so a small deeply nested JSON document can consume excessive memory. This path is the default when Cpanel::JSON::XS is not installed or `MOJO_NO_JSON_XS=1` is set; the Cpanel::JSON::XS fast path is not affected. Any caller that decodes an untrusted JSON body, for example `Mojo::Message::json` reached through `$c->req->json`, can exhaust process memory and cause denial of service.

NAME

Mojo::IOLoop::Trigger - IOLoop Trigger

SYNOPSIS

use Mojo::IOLoop::Trigger;

# Synchronize multiple events
my $t = Mojo::IOLoop::Trigger->new;
$t->on(done => sub { print "BOOM!\n" });
for my $i (1 .. 10) {
  $t->begin;
  Mojo::IOLoop->timer($i => sub {
    print 10 - $i, "\n";
    $t->end;
  });
}

# Stop automatically when done
$t->start;

DESCRIPTION

Mojo::IOLoop::Trigger is a remote control for Mojo::IOLoop. Note that this module is EXPERIMENTAL and might change without warning!

ATTRIBUTES

Mojo::IOLoop::Trigger implements the following attributes.

ioloop

my $ioloop = $t->ioloop;
$t         = $t->ioloop(Mojo::IOLoop->new);

Loop object to control, defaults to a Mojo::IOLoop object.

METHODS

Mojo::IOLoop::Trigger inherits all methods from Mojo::IOLoop::EventEmitter and implements the following new ones.

begin

my $cb = $t->begin;

Increment active event counter, the returned callback can be used instead of end.

my $t = Mojo::IOLoop->trigger;
Mojo::IOLoop->resolver->lookup('mojolicio.us' => $t->begin);
my $address = $t->start;

end

$t->end;
$t->end(@args);

Decrement active event counter.

start

my @args = $t->start;

Start ioloop and register done event that stops it again once the active event counter reaches zero.

EVENTS

Mojo::IOLoop::Trigger can emit the following events.

done

Emitted once the active event counter reaches zero.

SEE ALSO

Mojolicious, Mojolicious::Guides, http://mojolicio.us.