Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-15747: CWE-204 Observable Response Discrepancy in SRI Mojolicious

0
High
VulnerabilityCVE-2026-15747cvecve-2026-15747cwe-204cwe-352
Published: 07/14/2026 (07/14/2026, 17:07:32 UTC)
Source: CVE Database V5
Vendor/Project: SRI
Product: Mojolicious

Description

Mojolicious versions from 4.59 up to but not including 9.48 for Perl have a vulnerability where the session CSRF token is exposed to a BREACH compression oracle. The token is generated once per session and reused, and is included in a hidden form field. When responses containing this token also reflect attacker-controlled input and are gzip-compressed, an attacker can exploit compression length differences to recover the CSRF token and bypass CSRF protections.

Affected software

GitHub Actionsmore threats →cve
Mojolicious
pkg:github/Mojolicious
Affected versions
>=4.59 <9.48

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/15/2026, 00:49:09 UTC

Technical Analysis

This vulnerability in Mojolicious affects versions from 4.59 before 9.48 for Perl. The _csrf_token method generates a single token per session that is reused and placed in a hidden input field by _csrf_field. When responses containing this token also echo attacker-controlled input and are gzip-compressed, the compression length variations can be used as a BREACH oracle to recover the CSRF token. An attacker who can query such responses can extract the token and bypass csrf_protect validation, potentially enabling cross-site request forgery attacks.

Potential Impact

An attacker able to send requests that cause the server to respond with gzip-compressed content containing both the CSRF token and attacker-controlled input can exploit compression side-channel attacks (BREACH) to recover the CSRF token. This allows the attacker to bypass CSRF protections, increasing the risk of unauthorized actions performed on behalf of authenticated users.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is documented in the provided data. Until a fix is available, consider disabling gzip compression on responses that include CSRF tokens or avoid reflecting attacker-controlled input in such responses to mitigate the risk.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
CPANSec
Date Reserved
2026-07-14T15:03:43.632Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a56768c68715ace43f08bb7

Added to database: 07/14/2026, 17:49:00 UTC

Last enriched: 07/15/2026, 00:49:09 UTC

Last updated: 07/15/2026, 00:49:09 UTC

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses