CVE-2025-48067

Details

A specially crafted HTTP Request to an affected upload endpoint that contains some form inputs only supposed to be used internally can be used to make OctoPrint move a file that it thinks is a freshly uploaded temporary one into its 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 removes any internal-only form inputs from incoming requests in the central file upload processor component.

Credits

This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi

OctoPrint versions up until and including 1.11.1 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.

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. 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.

CVE-2025-48067 has a CVSS score of 5.4 (Medium). The vector is reachable from an adjacent network, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.2); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been patched in version 1.11.2.

1. What is CVE-2025-48067? CVE-2025-48067 is a medium-severity security vulnerability in OctoPrint (pip), affecting versions < 1.11.2. It is fixed in 1.11.2.
2. How severe is CVE-2025-48067? CVE-2025-48067 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of OctoPrint are affected by CVE-2025-48067? OctoPrint (pip) versions < 1.11.2 is affected.
4. Is there a fix for CVE-2025-48067? Yes. CVE-2025-48067 is fixed in 1.11.2. Upgrade to this version or later.
5. Is CVE-2025-48067 exploitable, and should I be worried? Whether CVE-2025-48067 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-48067 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-48067? Upgrade OctoPrint to 1.11.2 or later.