OctoPrint provides a web interface for controlling consumer 3D printers. Prior to 1.11.8 and 2.0.0rc3, OctoPrint's custom Tornado upload handler and Flask with Werkzeug parse request parameters differently, allowing an attacker with FILE_UPLOAD permission to inject reserved internal upload fields through query parameters or parser differentials despite the earlier GHSA-m9jh-jf9h-x3h2 fix. The affected endpoints are /api/files/{local|sdcard}, /api/languages, /plugin/backup/restore, and /plugin/pluginmanager/upload_file. An attacker can make OctoPrint treat an arbitrary host file as a temporary upload, move it into a downloadable upload directory, disclose configuration secrets or other readable files, and remove runtime files in a way that can affect a later restart. This issue is fixed in versions 1.11.8 and 2.0.0rc3.
CVE-2026-54134
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(medium)
- EG Risk
- 36(Track)EG Risk 36/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 computedSeverity70% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
August 21, 2026
Advisory Details (5)
Auto-updated Aug 21, 20262.0.0rc3
Patch available: OctoPrint/OctoPrint 2.0.0rc3 (pre-release)
https://github.com/OctoPrint/OctoPrint/releases/tag/2.0.0rc31.11.8
Patch available: OctoPrint/OctoPrint 1.11.8
https://github.com/OctoPrint/OctoPrint/releases/tag/1.11.8commit 8e3348197db8 (OctoPrint/OctoPrint)
Fix landed in OctoPrint/OctoPrint commit 8e3348197db8 — awaiting tagged release
https://github.com/OctoPrint/OctoPrint/commit/8e3348197db867c30a32d13984f0bd0d664be413commit 579148beeb6d (OctoPrint/OctoPrint)
Fix landed in OctoPrint/OctoPrint commit 579148beeb6d — awaiting tagged release
https://github.com/OctoPrint/OctoPrint/commit/579148beeb6d6e9b3d41b1cf32309b47218ed380File exfiltration possible via further parameter injection on upload endpoints · Advisory · OctoPrint/OctoPrint · GitHub
Affected: version 1.11.8 and 2.0.0rc3.
https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-j4h9-pm27-4rfwVendor Advisories for CVE-2026-54134(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| octoprint | 1.10.0 ... 2.0.0rc2 (84 versions) | 2.0.0rc3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× 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-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:05 UTCEG score recompute
- 2026-08-23 03:21 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 19:24 UTCEG score recompute
- 2026-08-21 18:30 UTCEG score recompute▲ 7.00
- 2026-08-21 18:29 UTCMITRE cvelistV5CVSS v3 → 7 · CVSS v4 → 7
- 2026-08-01 17:01 UTCEG score recompute
- 2026-07-26 15:52 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-06-23 18:21 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-73
- CVE-2022-24900EG 9.9EPSS p95CRITICAL
- CVE-2020-37080EG 9.8CRITICAL
- CVE-2023-4634EG 9.8EPSS p100CRITICAL
- CVE-2023-4191EG 9.8CRITICAL
- CVE-2022-39952EG 9.8EPSS p100CRITICAL
- CVE-2014-125059NVD 5.0EG 9.8CRITICAL
- CVE-2014-125044NVD 6.3EG 9.8CRITICAL
- CVE-2022-45213NVD 5.3EG 9.8CRITICAL
- CVE-2021-38477EG 9.8CRITICAL
- CVE-2020-1631NVD 8.8EG 9.8 KEVEPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-54134?
When was CVE-2026-54134 disclosed?
Is CVE-2026-54134 actively exploited?
What is the CVSS score of CVE-2026-54134?
How do I remediate CVE-2026-54134?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54134
Is Your Infrastructure Affected by CVE-2026-54134?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.