CVE-2025-32788

Details

An authentication bypass vulnerability exists in the following functions defined in octoprint/server/util/init.py:

• require_login
• require_login_with
• require_fresh_login_with

By adding the HTTP header X-Preemptive-Recording: yes to HTTP requests, these functions allow requests to proceed without redirecting to the login screen, effectively bypassing the login mechanism in the frontend. However, this only grants access to frontend page content, while authenticated API endpoints still enforce proper session validation.

Credits

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

OctoPrint versions up until and including 1.10.3 contain a vulnerability that allows an attacker to bypass the login redirect and directly access the rendered HTML of certain frontend pages.

The impact on data exposure is minimal because, typically, data is loaded via API requests that correctly enforce user authentication. In the current codebase, cases where data is directly embedded in the page content are rare. However, one notable exception is the authenticated variant of the reverse proxy test page, which displays the IP addresses of configured reverse proxies.

The primary risk lies in potential future modifications to the codebase that might incorrectly rely on the vulnerable internal functions for authentication checks, leading to security vulnerabilities.

CVE-2025-32788 has a CVSS score of 4.3 (Medium). The vector is reachable from an adjacent network, no 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.0); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been patched in version 1.11.0.

1. What is CVE-2025-32788? CVE-2025-32788 is a medium-severity security vulnerability in octoprint (pip), affecting versions <= 1.10.3. It is fixed in 1.11.0.
2. How severe is CVE-2025-32788? CVE-2025-32788 has a CVSS score of 4.3 (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-32788? octoprint (pip) versions <= 1.10.3 is affected.
4. Is there a fix for CVE-2025-32788? Yes. CVE-2025-32788 is fixed in 1.11.0. Upgrade to this version or later.
5. Is CVE-2025-32788 exploitable, and should I be worried? Whether CVE-2025-32788 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-32788 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-32788? Upgrade octoprint to 1.11.0 or later.