Fuel CMS vulnerabilities: known CVEs & security history
Fuel CMS · Actively exploited · 6 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Fuel CMS release lines — 6 in total. A CVE here doesn't mean your version is affected — check Fuel CMS's current status and the safe version to run.
Known Fuel CMS CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-30457 | critical | 9.8 | 1% | 2026 |
| CVE-2026-30458 | critical | 9.1 | 0% | 2026 |
| CVE-2026-30460 | high | 8.8 | 1% | 2026 |
| CVE-2026-30461 | high | 8.3 | 1% | 2026 |
| CVE-2026-30463 | high | 7.7 | 0% | 2026 |
| CVE-2026-30459 | high | 7.1 | 0% | 2026 |
Is my Fuel CMS version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Fuel CMS version → · Monitor Fuel CMS for new CVEs →
Fuel CMS vulnerabilities — frequently asked
How many known vulnerabilities does Fuel CMS have?
IsItPatched tracks 6 CVEs for Fuel CMS. 2 are critical-severity and 4 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Fuel CMS have any actively-exploited vulnerabilities?
None of Fuel CMS's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Fuel CMS vulnerability?
Among tracked issues, CVE-2026-30457 (CRITICAL, CVSS 9.8) ranks highest — a Code injection weakness.
Is Fuel CMS safe to use?
It depends on the version. The latest supported Fuel CMS release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Fuel CMS security status · Fuel CMS end-of-life · actively-exploited CVEs. Always verify against Fuel CMS's advisories — see our disclaimer.