Vulnerability in OctoPrint (CVE-2026-35163)
Summary
Vulnerability in OctoPrint (CVE-2026-35163). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.0rc3 or later.
Original description
The description as published by the source.
Impact
OctoPrint versions up to and including 1.11.7 as well as 2.0.0rc1 and 2.0.0rc2 are affected by a vulnerability that allows injection of arbitrary HTML and JavaScript into Suppressed Command notifications popups generated by the printer.
An attacker who successfully convinces a victim to print a specially crafted file could exploit this issue to disrupt ongoing prints, extract information (including sensitive configuration settings, if the targeted user has the necessary permissions for that), or perform other actions on behalf of the targeted user within the OctoPrint instance.
Patches
The vulnerability has been patched in version 1.11.8 and 2.0.0rc3.
Workaround
OctoPrint administrators can mitigate the risk by disabling popups:
- for Action Command notifications, set OctoPrint Settings -> Serial Connection -> Behaviour -> Sanity Checking -> Display notifications for suppressed commands to Never show notifications
It is also strongly recommended to ensure that files being printed originate from trusted sources, and, whenever possible, are sliced with an application's own slicer.
Credits
This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.
Timeline
2026-03-18: Report received
2026-04-01: Report verified
2026-04-01: Fix ready for 2.0.0
2026-06-22: Fix backported to 1.11.x
2026-06-23: Fix released with 1.11.8 and 2.0.0rc3
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-35163 has been found in OctoPrint.
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-35163" on the vendor's site.
CVE-2026-35163 (OctoPrint) — CWE-80
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-80) exists in OctoPrint.
Check the vendor advisory for the affected versions of OctoPrint.
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 でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com