Mojolicious is a real-time web framework for Perl. Prior to 9.47, the pure-Perl implementation of Mojo::JSON does not limit nesting depth when Cpanel::JSON::XS is unavailable or MOJO_NO_JSON_XS is enabled. An attacker who can supply untrusted JSON to decode_json, from_json, or j can submit deeply nested arrays or objects, causing unbounded recursion, memory exhaustion, and a process crash. Applications using the Cpanel::JSON::XS backend are not affected because that backend already enforces a nesting limit. This issue is fixed in version 9.47.
CVE-2026-68914
HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- 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
Mojolicious pure-Perl Mojo::JSON decoder allows memory exhaustion via deeply nested data · Advisory · mojolicious/mojo · GitHub
https://github.com/mojolicious/mojo/security/advisories/GHSA-p5qf-qvw8-xgvggithub_commit
commit cc38b0554275 (mojolicious/mojo)
Fix landed in mojolicious/mojo commit cc38b0554275 — awaiting tagged release
https://github.com/mojolicious/mojo/commit/cc38b0554275c4d84f6b8b49bcbbc1bec2068fe1Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-19 16:42 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
Frequently asked(5)
What is CVE-2026-68914?
CVE-2026-68914 is a high vulnerability published on September 18, 2026. Mojolicious is a real-time web framework for Perl. Prior to 9.47, the pure-Perl implementation of Mojo::JSON does not limit nesting depth when Cpanel::JSON::XS is unavailable or MOJONOJSONXS is enabled. An attacker who can supply untrusted JSON to decodejson, from_json, or j can submit deeply…
When was CVE-2026-68914 disclosed?
CVE-2026-68914 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-68914 actively exploited?
CVE-2026-68914 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 81.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68914?
CVE-2026-68914 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-68914?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68914, 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-68914
Is Your Infrastructure Affected by CVE-2026-68914?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.