After seven release candidates, OctoPrint 2.0.0 is now the stable release. It was published on GitHub on 16 November 2026, and it is the biggest structural change the print-server project has made in years. The headline feature is architectural: OctoPrint no longer assumes it is talking to a printer over a serial line. Printer communication now runs through "connectors" that plugins provide. The old communication layer has moved into a bundled Serial Connector plugin, and Moonraker and Bambu connectors are in development. The release also brings native printer-side storage, G-code thumbnails, HTTP API versioning, a reworked authentication-proxy setting and six security fixes. It also removes a long list of deprecated APIs, and the project has warned plugin authors that this will break some older plugins.

This article covers what is in the final 2.0.0 build and who should upgrade now.

The Connector Model

OctoPrint was built around one assumption for most of its life: a host computer sends G-code over USB serial to a Marlin-style firmware and reads the replies. Everything else depended on that link, including temperature graphs, file handling, pause and resume, and the plugin hooks that intercept commands.

In 2.0.0 that link is one option among several. The release notes describe connectors as plugin-provided components that handle connecting to a printer, fetching data from it, sending jobs to it and controlling it. The existing serial code now lives in the Serial Connector plugin, which ships with OctoPrint, so a standard USB setup should behave much as it always has. Two more connectors are being developed. The Moonraker Connector plugin targets printers that ship with Klipper and Moonraker. The Bambu Connector plugin targets the local API of Bambu Lab printers.

The release notes describe both as "in the works," and that wording matters. Upgrading to 2.0.0 today does not mean you can point OctoPrint at a Klipper or Bambu Lab machine. It means the foundation those integrations need has been released. If they arrive, OctoPrint becomes a front end that works across firmware ecosystems. Until now it has mostly been a serial host.

Storage, Thumbnails and Time Estimates

Several smaller features follow from the connector change. Printer-side storage has been turned into full native storage in OctoPrint's internal file manager, and plugins can add further storages. The file manager panel and the bundled Upload Manager plugin gain multi-storage support, and files and folders can be transferred between storages. This works with any connector that implements the necessary access methods.

Thumbnail support is now native too. A stand-alone gcode-thumbnail-tool extracts thumbnails from files in local storage, and the connector interface lets a connector fetch thumbnails for files stored inside the printer. Print-time estimates can now come from the connector as well. With the bundled Serial Connector plugin, M73 commands contained in the G-code file are used for the estimate, so the slicer's own prediction can drive the progress display.

API and Security Changes

The HTTP API now has versioning. Clients can send an X-OctoPrint-Api-Version header naming the OctoPrint version whose API behaviour and data model they expect, and OctoPrint matches that. That gives client authors (mobile apps, dashboards, slicer integrations) a formal way to target a known API version as the platform changes.

Advertisement

Administrators who run OctoPrint behind a reverse proxy that handles login need to check one setting. The old accessControl.trustRemoteUser setting has been replaced by accessControl.trustedAuthProxies, a list of trusted authentication proxies. OctoPrint now evaluates the X-Remote-User header only if the request came through one of those proxies, which must also be among your trusted reverse proxies. The list is empty by default, matching the old default of off. If you had the old setting enabled, the list is filled in from your configured trusted reverse proxies, so the previous behavior carries over. The release notes advise checking before the upgrade that your trusted reverse proxy list is correct and contains your authentication proxy, and afterwards narrowing the authentication list to the proxies that actually provide authentication.

The release also fixes six disclosed vulnerabilities:

  • CVE-2026-123361 (High, 7.1): an unauthenticated denial of service through multipart parsing in the UploadStorageFallbackHandler.
  • CVE-2026-123365 (Moderate, 6.8): the language pack deletion endpoint could delete the base directory, for users with SETTINGS permission.
  • CVE-2026-123360 (Moderate, 5.9): the restore option in the first-run wizard could let someone take over a freshly installed instance.
  • CVE-2026-123362 (Moderate, 5.1): a regular-expression denial of service (ReDoS) in websocket subscriptions, which needs a valid user account and can stall the server for up to 30 seconds.
  • CVE-2026-123363 (Low, 2.4): a DOM-based XSS in the AppKeys dialog.
  • CVE-2026-123366 (Low, 2.1): the SLICE permission could start a print without the PRINT permission.

The unauthenticated DoS is the most serious for anyone whose instance can be reached from beyond a trusted LAN. The first-run wizard issue mostly affects new installs that sit unconfigured on a network.

Advertisement

What Breaks

OctoPrint 2.0.0 requires Python 3.9 or newer. Python 3.7 and 3.8 are dropped, though the 1.11.x branch still supports them. The release adds compatibility with Python 3.14 and 3.15. The command line changes too: running octoprint without a subcommand no longer works, so service files and scripts that do this need to call octoprint serve. The websocket subscribe command also no longer accepts regular expressions for its logs or messages parameters, only a plain term, a prefix (foo*), a suffix (*foo), or true and false.

Plugins are the bigger risk. The official migration guide says compatibility layers that were kept for most of a decade have been removed, and plugins that ignored deprecation warnings will break. It also says that all but one of the removed deprecated endpoints and functions have had a replacement available for a long time. Many changes are camelCase-to-snake_case renames. In octoprint.access.users.UserManager, for example, checkPassword becomes check_password, addUser becomes add_user and changeUserPassword becomes change_user_password. The guide says most plugins need to do nothing more than one or two things, and some need nothing at all. It recommends moving plugin packaging to pyproject.toml and checking for upcoming removals that already log deprecation warnings. The release notes also point plugin authors to a scanner tool by @jacopotediosi that finds deprecated usages and packaging problems.

The Plugin Manager has new filter options that hide plugins marked as commercial or AI-developed, for users who want to keep those out of their search results.

What It Means for Makers

If you run a plain USB-connected printer and use few plugins, 2.0.0 should be a manageable upgrade. Before upgrading, confirm your Python version, check the security fixes against how your instance is exposed, and update any service unit that starts octoprint without serve.

If you rely on a large set of plugins, especially older or unmaintained ones, wait until each plugin's maintainer confirms 2.0 compatibility. Back up your configuration first. Users behind an authenticating reverse proxy should verify their trusted reverse proxy list before upgrading, then tighten the authentication proxy list afterwards.

Owners of Klipper and Bambu printers should treat this release as groundwork for now. The connector architecture is here, but the Moonraker and Bambu connectors are not finished yet. When they ship, they will decide whether OctoPrint's plugin ecosystem can reach printers it has never supported.

Sources