Vulnerability in OctoPrint (CVE-2026-54134)
Summary
Vulnerability in OctoPrint (CVE-2026-54134). Risk of unauthorized operations or information disclosure. Exploitable via FILE_UPLOAD. Mitigation: upgrade to 2.0.0rc3 or later.
Original description
The description as published by the source.
Impact
OctoPrint versions up until and including 1.11.7 as well as 2.0.0rc1 and 2.0.0rc2 contain a vulnerability that allows an attacker with the FILE_UPLOAD permission to exfiltrate files from the host that OctoPrint has read access to, by moving them into the upload folder where they then can be downloaded from. This vulnerability was already reported as GHSA-m9jh-jf9h-x3h2/CVE-2025-48067 but the fix provided in OctoPrint 1.11.2 turned out to be incomplete.
The primary risk lies in the potential exfiltration of secrets stored inside OctoPrint's config, or further system files. By removing important runtime files, this could also be used to impact the availability of the host after an attempted server restart. Given that the attacker requires a user account with file upload permissions, the actual impact of this should however hopefully be minimal in most cases.
Patches
The vulnerability has been patched in version 1.11.8 and 2.0.0rc3.
Details
OctoPrint's web application is implemented in Flask, but uploads are first intercepted by a custom upload handler built on Tornado that sits in front of it. The handler streams the upload to a temporary file on disk - so files larger than the available memory can be uploaded - and rewrites the request, adding internal form fields that tell Flask where to find that temporary file.
These fields are reserved and meant to be set only by t…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54134 has been found in OctoPrint.
Attackers can target a specific entry point like FILE_UPLOAD over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade OctoPrint to 2.0.0rc3 or later.
If unsure, ask your IT team or search "OctoPrint CVE-2026-54134" on the vendor's site.
CVE-2026-54134 (OctoPrint) — CWE-73
Attack surface: FILE_UPLOAD
Patched: 2.0.0rc3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in OctoPrint. Attackers reach the vulnerable code path via FILE_UPLOAD.
Check the vendor advisory for the affected versions of OctoPrint. Attack surface: FILE_UPLOAD.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.0.0rc3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OctoPrint' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OctoPrint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OctoPrintを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OctoPrint to 2.0.0rc3ステージング環境で 2.0.0rc3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。