Summary
Workaround
OctoPrint administrators can mitigate the risk by disabling popups:
- for Action Command notifications, uncheck OctoPrint Settings -> Printer Notifications -> Enable popups
- for Action Command prompts, set OctoPrint Settings -> Printer Dialogs -> Enable support -> Never
It is also strongly recommended to ensure that files being printed originate from trusted sources, and, whenever possible, are sliced with your own slicer.
Credits
This vulnerability was discovered and responsibly disclosed to OctoPrint by Jacopo Tediosi.
Impact
OctoPrint versions up to and including 1.11.3 are affected by a vulnerability that allows injection of arbitrary HTML and JavaScript into Action Command notification and prompt 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.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The vulnerability will be patched in version 1.11.4.
Frequently Asked Questions
- What is CVE-2025-64187? CVE-2025-64187 is a medium-severity cross-site scripting (XSS) vulnerability in octoprint (pip), affecting versions <= 1.11.3. It is fixed in 1.11.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of octoprint are affected by CVE-2025-64187? octoprint (pip) versions <= 1.11.3 is affected.
- Is there a fix for CVE-2025-64187? Yes. CVE-2025-64187 is fixed in 1.11.4. Upgrade to this version or later.
- Is CVE-2025-64187 exploitable, and should I be worried? Whether CVE-2025-64187 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
- What actually determines whether CVE-2025-64187 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.
- How do I fix CVE-2025-64187? Upgrade
octoprintto 1.11.4 or later.