Mojolicious
This hub aggregates every CVE we track for Mojolicious, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
10
CVEs tracked
4
Critical
2
High
0
In CISA KEV
Severity distribution
MEDIUM4CRITICAL4HIGH2
Monthly trend
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
1
2024-082026-07
Latest CVEs
The 10 most recently published vulnerabilities affecting Mojolicious.
- CVE-2026-15747Mojolicious versions from 4.59 before 9.48 for Perl expose a stable representation of the session CSRF token to a BREACH compression oracle9.1
- CVE-2024-58134Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default8.1
- CVE-2024-58135Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default5.3
- CVE-2021-47208The Mojolicious module before 9.11 for Perl has a bug in format detection that can potentially be exploited for denial of service.4.3
- CVE-2020-36829The Mojolicious module before 8.65 for Perl is vulnerable to secure_compare timing attacks that allow an attacker to guess the length of a secret string. Only versions after 1.74 are affected.7.5
- CVE-2011-1841Cross-site scripting (XSS) vulnerability in the link_to helper in Mojolicious before 1.12 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.4.3
- CVE-2010-4802Commands.pm in Mojolicious before 0.999928 does not properly perform CGI environment detection, which has unspecified impact and remote attack vectors.10.0
- CVE-2010-4803Mojolicious before 0.999927 does not properly implement HMAC-MD5 checksums, which has unspecified impact and remote attack vectors.10.0
- CVE-2009-5074Unspecified vulnerability in the MojoX::Dispatcher::Static implementation in Mojolicious before 0.991250 has unknown impact and attack vectors.10.0
- CVE-2011-1589Directory traversal vulnerability in Path.pm in Mojolicious before 1.16 allows remote attackers to read arbitrary files via a %2f..%2f (encoded slash dot dot slash) in a URI.5.0
Product normalization is registry-driven with AI assist and human review. How it works