← Back
CVE-2025-58180
OS Command Injection in octoprint (CVE-2025-58180)
Summary
OS command injection in octoprint (CVE-2025-58180). Successful exploitation can lead to full system takeover. Exploitable via ``enabled``. Mitigation: upgrade to `1.11.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-58180** has been found in octoprint.
Attackers can target a specific entry point like ``enabled`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade octoprint to **1.11.3** or later.
If unsure, ask your IT team or search "octoprint CVE-2025-58180" on the vendor's site.
CVE-2025-58180 (octoprint) — CWE-78 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `enabled` / `False` / `feature.enforceReallyUniversalFilenames` / `true`
Patched: `1.11.3` — 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.
❓ What is the problem
**OS command injection** (CWE-78) exists in octoprint. Attackers reach the vulnerable code path via ``enabled`` without authentication.
📍 Affected scope
octoprint — . Attack surface: `enabled` / `False` / `feature.enforceReallyUniversalFilenames` / `true`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.11.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade octoprint to 1.11.3ステージング環境で 1.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
octoprint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-58180
- advisory https://github.com/advisories/GHSA-49mj-x8jp-qvfc
- package https://github.com/OctoPrint/OctoPrint
- package https://pypi.org/project/octoprint
- web https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-49mj-x8jp-qvfc
- web https://github.com/OctoPrint/OctoPrint/commit/be4201ef58d9a7c03593252398c16eada90a258b
- web https://github.com/OctoPrint/OctoPrint/commit/c3a940962f4658a8e035a00388781b1cbd768841
- web https://github.com/OctoPrint/OctoPrint/releases/tag/1.11.3