2026.09.2 — 2026-09-06

Security

• Cluster-scoped reads now honour your grants. Six read endpoints — the cross-node queue grid, the addresses / consumers / sessions / connections / producers views, the metrics timeseries, the audit trail, and the broker event history — did not check whether the caller held a grant on the cluster they addressed. Any signed-in user could read any registered cluster's queues, metrics, audit trail, and events by putting its id in the URL, regardless of the roles they had been given. They are now checked like every other cluster-addressed read, and a cluster you hold no grant on answers 404 rather than revealing that it exists.

  After upgrading, users whose grants are scoped to specific clusters or environments will lose access to data they could previously see. That is the fix working. If someone genuinely needs cross-cluster visibility, grant them the role at global scope (Administration → Users). Users holding a global grant are unaffected.