RabbitMQ OAuth credential refresh retains revoked runtime tags (CVE-2026-67420) | HOL Guard CVE

Low · CVSS 2.3CVE-2026-67420

RabbitMQ OAuth credential refresh retains revoked runtime tags

Answer in brief

CVE-2026-67420 records a Low severity (CVSS 2.3) vulnerability in RabbitMQ OAuth credential refresh retains revoked runtime tags. The current sources do not mark it as known exploited. The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
rabbitmq/rabbitmq-servergeneric	>=3.13.0 <3.13.19 \|\| >=4.0.0 <4.0.24 \|\| >=4.1.0 <4.1.15 \|\| >=4.2.0 <4.2.10 \|\| >=4.3.0 <4.3.5	3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5

Recommended response

Check inventory. Check lockfiles and deployed manifests for rabbitmq/rabbitmq-server.
Review the reported fix. Update rabbitmq/rabbitmq-server to 3.13.19 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.