Prusa Research has pushed stable firmware 8.0.2 for its Buddy-based printers, published on GitHub around 12:02 UTC on 16 November 2026. It is a maintenance release rather than a feature drop, but it is a wide one: every current Buddy machine is covered, from the CORE One family through the XL, MK4, MK3.9, MK3.5 and MINI. The notes list three crash fixes, a new manual Printer Type setting for the XL family, and a single line saying that security issues in the handling of USB devices, USB drives, PrusaLink and Prusa Connect have been fixed. Roughly two hours later, Prusa also posted an 8.0.3 beta aimed only at the CORE One line, reworking how those printers calibrate sensorless homing.

Who Gets It

The 8.0.2 release names sixteen models: CORE One L+, CORE One L, CORE One+ (Gen 2) INDX, CORE One INDX, CORE One+ (Gen 2), CORE One, XL+, XL, MK4S, MK4, MK3.9S, MK3.9, MK3.5S, MK3.5, MINI+ and MINI. That is effectively the whole lineup running the Buddy board.

There is a wrinkle in the version numbering. An intermediate 8.0.1 build shipped only for the XL, XL+, MINI and MINI+. Version 8.0.2 folds those 8.0.1 fixes in, so owners of a CORE One or an MK4S who never saw 8.0.1 get its changes now without having missed anything.

The Security Line

The item most owners should care about is the shortest one in the changelog. Prusa says only that it "fixed security issues in the handling of USB devices, USB drives, PrusaLink and Prusa Connect." The notes do not describe the individual flaws, their severity, or how they could be triggered, and FilamentFeed has no further detail to add beyond that sentence.

Even without specifics, the list of affected surfaces tells you something about exposure. USB devices and drives are the physical path: anything plugged into the printer's port, including a stick handed over by someone else at a makerspace or print farm. PrusaLink is the printer's local network interface, and Prusa Connect is the cloud service that lets owners monitor and start jobs remotely. Those two are the network-facing paths. A printer that is on a shared LAN, reachable through Connect, or fed G-code from drives of uncertain origin touches at least one of these areas. That covers a large share of installed machines, and it is the main reason this point release is worth installing promptly rather than whenever convenient.

A Manual Override for XL Identity

The one genuinely new setting is aimed at the XL family. At every start, the printer detects whether it is an XL or an XL+ based on whether it finds the XL-CAN bridge. If the detection gives the wrong result, the type can now be set under Settings > Hardware > Printer Type, which offers three values: Auto, XL and XL+. Auto is the default and keeps the automatic detection, showing the type detected at the last start in parentheses, for example Auto (XL+). The manual options force the printer to run as an XL or an XL+. After a change, the printer asks whether to restart, because the new type takes full effect only after a restart.

The release notes tie this to the XL-CAN bridge. While the type is set manually, the printer still looks for the bridge at every start. If the result does not match the selected type, a Printer Type Mismatch warning appears, so, as the notes put it, a disconnected XL-CAN bridge on an XL+ does not go unnoticed. In practice, that gives owners a way to pin the identity of a machine and get an explicit warning when the hardware and the configuration disagree. The notes do not go into the scenarios that prompted the change, so treat it as a tool to reach for if your XL or XL+ is misidentifying itself, not something every owner needs to touch.

Advertisement

Three Crashes Closed

The remaining fixes are all crash cases, each with a clear trigger:

  • Crash detection during homing. If crash detection fired while the printer was homing, the printer could stop with a blue error screen (issue #5530). The notes say this mostly happened on the XL when it homed while recovering from a filament runout or a stuck filament. Prusa's fix is to pause crash detection during homing moves, so the two mechanisms no longer collide.
  • MMU First Layer Calibration. On MMU3 setups, First Layer Calibration could stop with a blue error screen when the printer did not know which MMU slot was loaded, for example after a restart with filament already in the extruder (issue #5552). The calibration now uses the filament set for the first MMU slot.
  • Incomplete OpenPrintTag spools. On the CORE One and CORE One L, an OpenPrintTag missing some information, for example one with neither a material type nor a material abbreviation, could crash the printer each time the spool was placed on the reader. The filament prompt now opens and leaves the missing information blank.

None of these is exotic. Homing and first-layer calibration happen constantly, and a reader that is meant to accept spools from many sources has to cope with imperfect tags. Removing hard crashes from those everyday paths is exactly what a point release is for.

The 8.0.3 Beta: Homing Calibration for CORE One

Separately, Prusa published 8.0.3-beta around 14:00 UTC the same day. It targets only four models: CORE One+ (Gen 2) INDX, CORE One INDX, CORE One+ (Gen 2) and CORE One. Notably, the CORE One L variants are not on that list.

Advertisement

The change (issue #5520) concerns homing calibration. Previously, calibration used a single motor current, so it could fail on some printers. The beta keeps the same first step, searching for a working sensitivity value at the default motor current, but if that does not succeed it repeats the search with a second current setting. Prusa says this makes calibration work on most motor combinations. The trade-off is time: when the second current setting is needed, calibration takes longer than before.

That is a sensible design. Printers whose motors calibrate cleanly at the default current should see no difference, while the ones that previously failed get a second chance instead of an error. As with any beta, though, it is aimed at owners who have actually hit the problem or who are comfortable reporting issues back, not at production machines that are already homing reliably.

What It Means for Makers

For most owners, the decision is simple: install 8.0.2. It runs across the whole Buddy range, it closes crash cases in routine operations, and it addresses security issues in exactly the interfaces that connect a printer to drives, local networks and the cloud. The lack of detail on those flaws is a reason to update, not to wait for more information.

XL and XL+ owners get one extra thing to check. If the machine has been identifying itself correctly, Auto remains the default and nothing needs changing. If it has not, the new Printer Type setting and its mismatch warning give a direct way to set things straight.

CORE One owners who have struggled with homing calibration failures have a candidate fix in 8.0.3-beta, with the caveat of longer calibration when the second current is needed. Everyone else on a CORE One can stay on stable 8.0.2 and let the beta mature into a full release.

Sources