Skip to main content
CVE-2026-15747VulnerabilityPublished Updated

SUSE · Security update for perl-Mojolicious

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2026-15747· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade SUSE Mojolicious to 9.48 as a priority.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.48
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade Mojolicious to 9.48.

Affected software

ProductAffectedFixed in
SRIMojoliciousAffected
  • >=4.59 <9.48
Fixed in
  • 9.48
GitHubMojoliciouspkg:github/MojoliciousOther threatsAffected
  • >=4.59 <9.48
Fixed in
  • 9.48

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade perl-Mojolicious to version 9.480.0 or later, which includes the fix for the CSRF token BREACH vulnerability. The update also includes other security and stability improvements. No additional mitigation is required beyond applying this official update.

Description

A security update for perl-Mojolicious addresses a vulnerability (CVE-2026-15747) where CSRF tokens were susceptible to BREACH attacks. The update changes token handling to use a fresh random mask on every request instead of reusing tokens for the session lifetime. Additional fixes include limiting JSON decoding depth to prevent memory exhaustion and various other improvements and bug fixes.

References

Community reviews

Loading reviews…