RabbitMQ OAuth credential refresh retains revoked runtime tags

Summary

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ OAuth credential refresh retains revoked runtime tags. when an existing AMQP connection refreshes from an OAuth token that grants the impersonator tag to a valid same-username token that no longer grants that tag, RabbitMQ updates the OAuth backend implementation (token/scopes/expiry) but leaves the connection's runtime #user.tags unchanged. rabbitaccesscontrol:checkuserid/2 then still honors the stale impersonator tag, so the connection (including newly opened channels) can continue publishing messages with a foreign AMQP userid after that privilege should have been revoked. A fresh connection using the downgraded token correctly refuses the same publish, proving the defect is stale session state rather than the token Limited to connections that once held impersonator and successfully refresh to a downgraded same-username rabbitauthbackendoauth2 (or an equivalent refresh-capable backend that returns tags) is enabled for This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.

Timeline

1. Sep 25, 2026, 4:42 PM UTCCVE published
2. Sep 29, 2026, 7:31 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Sep 29, 2026, 7:32 PM UTCRecord last updated

Affected versions

• rabbitmq rabbitmq-server

  From 3.13.0 · fixed in 3.13.19; From 4.0.0 · fixed in 4.0.24; From 4.1.0 · fixed in 4.1.15; From 4.2.0 · fixed in 4.2.10; From 4.3.0 · fixed in 4.3.5

• rabbitmqBitnami

  From 3.13.0 · fixed in 3.13.19; From 4.0.0 · fixed in 4.0.24; From 4.1.0 · fixed in 4.1.15; From 4.2.0 · fixed in 4.2.10; From 4.3.0 · fixed in 4.3.5

References 3