Post-revocation message disclosure via persistent consumers
Published Jul 10, 2026 · Updated Jul 10, 2026
Incorrect authorization in RabbitMQ Server 4.2.0 through 4.2.5 allows remote authenticated users to read messages after OAuth revocation. The AMQP 0-9-1 channel update handler replaces its user state but neither cancels existing consumers nor rechecks authorization before basic.deliver sends later messages. Exploitation requires a consumer created with valid read scope and an expired or scope-reduced token; only messages delivered to that existing consumer are exposed.
Summary
What happened
Incorrect authorization in RabbitMQ Server 4.2.0 through 4.2.5 allows remote authenticated users to read messages after OAuth revocation. The AMQP 0-9-1 channel update handler replaces its user state but neither cancels existing consumers nor rechecks authorization before basic.deliver sends later messages. Exploitation requires a consumer created with valid read scope and an expired or scope-reduced token; only messages delivered to that existing consumer are exposed.
The record
- CVE
- CVE-2026-57218
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- RabbitMQ
- Product
- RabbitMQ Server
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.2.0, < 4.2.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OAuth consumer persistence proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo