CVE-2026-54134: OctoPrint OctoPrint Has Possible File Exfiltration Vulnerability

HIGH
Advisory Identifier: GHSA-j4h9-pm27-4rfw
CWE-436 CWE-73
Published
Advisory Summary

CVE-2026-54134 is a HIGH octoprint has possible file exfiltration vulnerability (CWE-436: Interpretation Conflict) affecting OctoPrint libraries in the PyPI ecosystem. The issue involves octoprint has possible file exfiltration via query parameters on upload endpoints. Remediation is available by upgrading affected packages to version 1.11.8, 2.0.0rc3.

CVE-2026-54134 at a Glance

CVE Identifier CVE-2026-54134
GHSA Identifier GHSA-j4h9-pm27-4rfw
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-436: Interpretation Conflict
Affected Product OctoPrint
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-54134

To remediate this vulnerability, upgrade all affected OctoPrint dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

OctoPrint fixed: 1.11.8
pip install OctoPrint>=1.11.8
OctoPrint fixed: 2.0.0rc3
pip install OctoPrint>=2.0.0rc3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show OctoPrint

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-54134, inspect your installed packages using pip:

pip show OctoPrint

Analyze the terminal output to locate any version of OctoPrint in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.11.8), your application is affected.

Note: The pip show OctoPrint command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-436: Interpretation Conflict, where product a handles inputs or steps differently than product b, which causes a to perform incorrect actions based on its perception of b's state. In OctoPrint, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-m9jh-jf9h-x3h2) 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 the upload handler, never by the client. The previous fix from [GHSA-m9jh-jf9h-x3h2/CVE-2025-48067](https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-m9jh-jf9h-x3h2) stripped them from the request received from the client when they were sent as multipart form fields, yet they could still reach Flask through other channels: as plain query parameters, or - since the Tornado handler and Flask did not parse requests identically - smuggled in via several "parser differentials" that looked harmless to the handler while Flask still saw the injected fields. Any of these let an attacker make OctoPrint treat an arbitrary file on the host as a freshly uploaded one and move it into the upload folder. The following endpoints in OctoPrint are affected: - `/api/files/{local|sdcard}` - `/api/languages` - `/plugin/backup/restore` - `/plugin/pluginmanager/upload_file` Further upload endpoints in third party plugins might be affected too. The fix rejects requests carrying any of the reserved fields, aligns the Tornado handler's request parsing with Flask's (Werkzeug) to avoid any differential parsing, and re-validates the request rewritten by Tornado before forwarding it to Flask. ### Credits This vulnerability was discovered and responsibly disclosed to OctoPrint by Koh Jun Sheng and Jacopo Tediosi. ### Timeline 2026-06-04: Report received 2026-06-04: Report acknowledged 2026-06-08: Report verified 2026-06-17: Fix ready for 1.11.x 2026-06-22: Fix ported to 2.0.0 2026-06-23: Fix released with 1.11.8 and 2.0.0rc3

CVE-2026-54134 Affected OctoPrint Versions

2 component(s)
Fixed Versions:
1.11.82.0.0rc3
Product / Package Ecosystem Affected Versions Fixed Version
OctoPrint
PyPI
< 1.11.8
1.11.8
OctoPrint
PyPI
≥ 2.0.0rc1
< 2.0.0rc3
2.0.0rc3

References

Frequently Asked Questions

What is CVE-2026-54134?
CVE-2026-54134 is a security vulnerability in OctoPrint involving OctoPrint has possible file exfiltration via query parameters on upload endpoints under CWE-436: Interpretation Conflict.
Which OctoPrint versions are affected?
Affected versions include releases prior to 1.11.8, 2.0.0rc3 across affected packages: OctoPrint.
What version fixes CVE-2026-54134?
Upgrading to 1.11.8, 2.0.0rc3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is OctoPrint affected?
Yes, OctoPrint is affected in releases prior to 1.11.8, 2.0.0rc3. Upgrade your dependency to 1.11.8, 2.0.0rc3 or later.
What CWE is associated with CVE-2026-54134?
CVE-2026-54134 is classified under CWE-436: Interpretation Conflict (Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.).
How can I check PyPI dependencies for CVE-2026-54134?
Run the dependency tree command: 'pip show OctoPrint'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j4h9-pm27-4rfw",
  "modified" : "2026-08-21T18:28:35Z",
  "published" : "2026-06-23T18:03:54Z",
  "aliases" : [ "CVE-2026-54134" ],
  "summary" : "OctoPrint has possible file exfiltration via query parameters on upload endpoints",
  "details" : "### Impact\n\nOctoPrint 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](https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-m9jh-jf9h-x3h2) but the fix provided in OctoPrint 1.11.2 turned out to be incomplete.\n\nThe 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.\n\n### Patches\n\nThe vulnerability has been patched in version 1.11.8 and 2.0.0rc3.\n\n### Details\n\nOctoPrint'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.\n\nThese fields are reserved and meant to be set only by the upload handler, never by the client. The previous fix from [GHSA-m9jh-jf9h-x3h2/CVE-2025-48067](https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-m9jh-jf9h-x3h2) stripped them from the request received from the client when they were sent as multipart form fields, yet they could still reach Flask through other channels: as plain query parameters, or - since the Tornado handler and Flask did not parse requests identically - smuggled in via several \"parser differentials\" that looked harmless to the handler while Flask still saw the injected fields. Any of these let an attacker make OctoPrint treat an arbitrary file on the host as a freshly uploaded one and move it into the upload folder.\n\nThe following endpoints in OctoPrint are affected:\n\n- `/api/files/{local|sdcard}`\n- `/api/languages`\n- `/plugin/backup/restore`\n- `/plugin/pluginmanager/upload_file`\n\nFurther upload endpoints in third party plugins might be affected too.\n\nThe fix rejects requests carrying any of the reserved fields, aligns the Tornado handler's request parsing with Flask's (Werkzeug) to avoid any differential parsing, and re-validates the request rewritten by Tornado before forwarding it to Flask.\n\n### Credits\n\nThis vulnerability was discovered and responsibly disclosed to OctoPrint by Koh Jun Sheng and Jacopo Tediosi.\n\n### Timeline\n\n2026-06-04: Report received\n2026-06-04: Report acknowledged\n2026-06-08: Report verified\n2026-06-17: Fix ready for 1.11.x\n2026-06-22: Fix ported to 2.0.0\n2026-06-23: Fix released with 1.11.8 and 2.0.0rc3",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "OctoPrint"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.11.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.11.7"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "OctoPrint"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0rc1"
      }, {
        "fixed" : "2.0.0rc3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.0rc2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-j4h9-pm27-4rfw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54134"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OctoPrint/OctoPrint"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/octoprint/PYSEC-2026-2687.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-436", "CWE-73" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-23T18:03:54Z",
    "nvd_published_at" : null
  }
}