Patching a broker the fleet can't be scheduled around
Edge device fleets run RabbitMQ on a hardware refresh cycle measured in years, not sprints. Patches have to land on the broker version already qualified for the fleet.
Challenge
The broker version is locked to whatever shipped on the device firmware. A CVE fix that arrives as "upgrade to the latest release" is not an option when the fleet itself won't be touched again until the next hardware cycle.
Environment
RabbitMQ embedded in or fronting a device fleet, where the broker version is effectively frozen between firmware releases.
Approach
The fix is backported onto the exact broker version the fleet already runs, so the patch ships without requiring a firmware-level change or a fleet-wide qualification pass.
What this delivers
CVE coverage that moves at the pace of a software patch, not a hardware refresh cycle.