ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-67420

RabbitMQ OAuth credential refresh retains revoked runtime tags

Published Oct 1, 2026 · catalog updated Oct 17, 2026 · RabbitMQ OAuth credential refresh

Check if you run it

No confirmed exploitation is on record for CVE-2026-67420. EPSS is 0.23%. Act only if a listed version of RabbitMQ OAuth credential refresh is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (RabbitMQ OAuth credential refresh).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.23%
Remediation
Advisory link
Affected products
Bitnami rabbitmq

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Bitnami rabbitmq3.13.0 → 3.13.19

How to fix CVE-2026-67420

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-67420. EPSS is 0.23%. Act only if a listed version of RabbitMQ OAuth credential refresh is installed.

Which versions are affected?

Compare what you have installed with 3.13.0 → 3.13.19. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.23%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 1, 2026 · GitHub Advisory Database

    Detected

    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/expir

  2. Oct 17, 2026 · GitHub Advisory Database

    Fix available

    rabbitmq fixed in 3.13.19

  3. Oct 17, 2026 · GitHub Advisory Database

    Fix available

    rabbitmq fixed in 3.13.19

  4. Oct 17, 2026 · GitHub Advisory Database

    Updated

    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/expir

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.