Mojolicious is a real-time web framework for Perl. Prior to 9.48, the Mojolicious CSRF helpers csrf_field, csrf_token, and csrf_protect reuse an unchanged per-session token in rendered HTML. When response compression is enabled and attacker-influenced content is reflected in the same response, an unauthenticated attacker who can induce many victim requests and observe response sizes can use a BREACH compression side channel to recover the token and forge cross-site requests. API-only deployments that never render the token in HTML are not affected. This issue is fixed in version 9.48.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-77568 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-15747. Reason: This candidate is a duplicate of CVE-2026-15747. Notes: All CVE users should reference CVE-2026-15747 instead of this candidate.
CVE-2026-77568
✕ Withdrawn — historical dataMEDIUMPre-NVD 4.2Trending — 3 sources updated this week
4.2CVSS
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026Patch available. Sources: github_commit, github.
github Patch Available
CSRF tokens in Mojolicious are vulnerable to BREACH attacks · Advisory · mojolicious/mojo · GitHub
https://github.com/mojolicious/mojo/security/advisories/GHSA-cf46-h6jw-mj3rgithub_commit
commit 01921fbbbbec (mojolicious/mojo)
Fix landed in mojolicious/mojo commit 01921fbbbbec — awaiting tagged release
https://github.com/mojolicious/mojo/commit/01921fbbbbeca2d1397e082d4a647f9b84c24e27Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-22 13:05 UTCEG score recompute▼ 4.20
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-19 17:06 UTCEG score recompute
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:29 UTCEG score recompute
- 2026-09-18 16:25 UTCEG score recompute
- 2026-09-18 16:15 UTCEG score recompute
- 2026-09-18 16:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77568?
CVE-2026-77568 is a medium vulnerability published on September 18, 2026. Mojolicious is a real-time web framework for Perl. Prior to 9.48, the Mojolicious CSRF helpers csrffield, csrftoken, and csrf_protect reuse an unchanged per-session token in rendered HTML. When response compression is enabled and attacker-influenced content is reflected in the same response, an…
When was CVE-2026-77568 disclosed?
CVE-2026-77568 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77568 actively exploited?
CVE-2026-77568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-77568?
CVE-2026-77568 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-77568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77568, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77568
Is Your Infrastructure Affected by CVE-2026-77568?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.