Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
rabbitmq rabbitmq-server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

RabbitMQ 是一个消息和流式处理代理。从 3.13.0 到 3.13.19、4.0.24、4.1.15、4.2.10 和 4.3.5 版本期间，RabbitMQ 的 OAuth 凭证刷新功能会保留已撤销的运行时标签（runtime tags）。 当现有的 AMQP 连接使用 OAuth 令牌进行刷新，且该令牌原本授予“模拟用户（impersonator）”标签，但刷新后使用的是同一用户名下不再授予该标签的有效令牌时，RabbitMQ 会更新 OAuth 后端实现（包括令牌、作用域和过期时间），但会保留连接运行

CVSS 2.3 · Low EPSS 0.24% · P13
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-67420

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
RabbitMQ OAuth credential refresh retains revoked runtime tags
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
rabbitmq rabbitmq-server >= 3.13.0, < 3.13.19 -

II. Public POCs for CVE-2026-67420

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-67420

请登录查看更多情报信息。

Other References for CVE-2026-67420 (3)

Same Patch Batch · rabbitmq · 2026-09-25 · 28 CVEs total

CVE-2026-67236 8.2 HIGH RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /
CVE-2026-67409 8.2 HIGH RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Au
CVE-2026-67410 8.2 HIGH RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
CVE-2026-67239 7.6 HIGH RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
CVE-2026-67237 7.5 HIGH RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint
CVE-2026-67408 7.1 HIGH RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node
CVE-2026-67419 7.1 HIGH RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
CVE-2026-67226 6.9 MEDIUM RabbitMQ: Admin-only atom exhaustion: PUT /api/users tags list
CVE-2026-61837 6.3 MEDIUM RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authent
CVE-2026-67242 6.3 MEDIUM RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp
CVE-2026-67230 6.3 MEDIUM RabbitMQ: Web-STOMP unbounded pre-auth accumulation
CVE-2026-67223 6.3 MEDIUM RabbitMQ: LDAP DN injection via unescaped substitution
CVE-2026-67225 6.3 MEDIUM RabbitMQ: Stream-protocol frame length never validated against frame_max
CVE-2026-67411 6.0 MEDIUM RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass
CVE-2026-66073 6.0 MEDIUM RabbitMQ: Atom table exhaustion via management API node field
CVE-2026-67412 6.0 MEDIUM RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message acces
CVE-2026-67413 6.0 MEDIUM RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an U
CVE-2026-66071 6.0 MEDIUM RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values
CVE-2026-67415 5.9 MEDIUM RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Servic
CVE-2026-67222 5.9 MEDIUM RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client

Showing top 20 of 28 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: rabbitmq-server
Same vendor: rabbitmq
Same weakness: CWE-862

V. Comments for CVE-2026-67420

No comments yet

Leave a comment