Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.24% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-67420High confidence
RabbitMQ OAuth credential refresh retains revoked runtime tags
rabbitmq · rabbitmq-server
Official source article: GitHub GHSA-86FM-44M9-RQJX ↗. Check the applicable product and release in the original source.
2.3LowCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productLow technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Medium, raised one band.upgradedsince 29 Sep 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs rabbitmq rabbitmq-server and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- SUSE Product Security Team: 118 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 3 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 3 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | rabbitmq-server | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | rabbitmq-server | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | rabbitmq-server | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | rabbitmq-server | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.3.6-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | rabbitmq-server | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 8 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-67420 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityrabbitmq-server: rabbitmq-server: Unauthorized user impersonation via stale OAuth token refresh
The vendor explicitly identifies these products as affected by this CVE.
- rabbitmq-server4.2.src as a component of Red Hat Hardened Images
- rabbitmq-server.src as a component of Red Hat OpenStack Platform 18.0
- Summary
- A flaw was found in rabbitmq-server. When an existing Advanced Message Queuing Protocol (AMQP) connection refreshes its authentication token to one with revoked impersonation privileges, the server fails to update the active session's security tags. As a result, an authenticated user can retain elevated permissions on existing connections and continue publishing messages under another user's identity.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE-2026-67420 · CSAF 2.0 · revision 2 · interimSUSE Product Security TeamCVE-2026-67420
The vendor explicitly identifies these products as affected by this CVE.
- erlang-rabbitmq-client as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- rabbitmq-server as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- rabbitmq-server-plugins as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- erlang-rabbitmq-client as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- rabbitmq-server as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- rabbitmq-server-plugins as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- erlang-rabbitmq-client as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- rabbitmq-server as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- rabbitmq-server-plugins as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- erlang-rabbitmq-client as component of SUSE Linux Enterprise High Performance Computing 15 SP4
- rabbitmq-server as component of SUSE Linux Enterprise High Performance Computing 15 SP4
- rabbitmq-server-plugins as component of SUSE Linux Enterprise High Performance Computing 15 SP4
- Summary
- 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.
- Remediation
- No remediation text is recorded.
Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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
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.
Why
The application reaches a protected operation without first confirming that the requester is authorised.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The application reaches a protected operation without first confirming that the requester is authorised.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
- Likely attack path
- a network path → Missing Authorization → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-862 ↗
CWE-862: Missing Authorization. The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VILowVulnerable-system integrity: A successful attack can cause a limited loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Fixed
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 25 Sept 2026 · Last source change 29 Sept 2026, 19:32 UTC · CWE-862 · Missing Authorization
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-26
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-87244
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enrichment underway
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- rabbitmq-server4.2.src as a component of Red Hat Hardened Images; rabbitmq-server as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server.src as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server.src as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 18.0 · Fixed: rabbitmq-server4.3-0:4.3.6-1.hum1@aarch64 as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@src as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@x86_64 as a component of Red Hat Hardened Images
- After
- rabbitmq-server4.2.src as a component of Red Hat Hardened Images; rabbitmq-server.src as a component of Red Hat OpenStack Platform 18.0 · Fixed: rabbitmq-server4.3-0:4.3.6-1.hum1@aarch64 as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@src as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@x86_64 as a component of Red Hat Hardened Images
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-67420.CNA ↗
- Before
- remediation: access.redhat.com/CVE-2026-67420
- After
- no authoritative guidance recorded
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- rabbitmq-server: >= 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 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- After
- rabbitmq-server: >= 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 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.CNA ↗
- Before
- Patch available
- After
- Awaiting fix
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.CVE.org ↗
- Before
- No public exploit
- After
- Public exploit reference
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- rabbitmq-server: >= 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 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- rabbitmq-server: >= 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 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-67420 to remediation: access.redhat.com/CVE-2026-67420.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-67420
- After
- remediation: access.redhat.com/CVE-2026-67420
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- rabbitmq-server4.2.src as a component of Red Hat Hardened Images; rabbitmq-server4.3.src as a component of Red Hat Hardened Images; rabbitmq-server as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server.src as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server.src as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 18.0
- After
- rabbitmq-server4.2.src as a component of Red Hat Hardened Images; rabbitmq-server as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server.src as a component of Red Hat OpenStack Platform 13 (Queens); rabbitmq-server as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server.src as a component of Red Hat OpenStack Platform 16.2; rabbitmq-server as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 17.1; rabbitmq-server.src as a component of Red Hat OpenStack Platform 18.0 · Fixed: rabbitmq-server4.3-0:4.3.6-1.hum1@aarch64 as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@src as a component of Red Hat Hardened Images; rabbitmq-server4.3-0:4.3.6-1.hum1@x86_64 as a component of Red Hat Hardened Images
- ENISA EUVD mappingEUVD-2026-87244 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-87244"}
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-67420.CNA ↗
- Before
- remediation: access.redhat.com/CVE-2026-67420
- After
- no authoritative guidance recorded
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- rabbitmq-server: >= 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 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- After
- rabbitmq-server: >= 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 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.CNA ↗
- Before
- Patch available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: wid.cert-bund.de/securityadvisory?name=WID-SEC-2026-2881.CNA ↗
- Before
- remediation: wid.cert-bund.de/securityadvisory?name=WID-SEC-2026-2881
- After
- no authoritative guidance recorded
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Open Source RabbitMQ <3.13.19; Open Source RabbitMQ <4.2.10; Open Source RabbitMQ <4.3.5; Open Source RabbitMQ <4.0.24; Open Source RabbitMQ <4.1.15 · Fixed: No fixed version is explicitly recorded in this authority advisory.
- After
- rabbitmq-server: >= 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 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- SeveritySeverity changed from Unknown to Low.CNA ↗
- Before
- Unknown
- After
- Low
- CVSS scoreCVSS score changed from not recorded to 2.3 (CVSS 4.0 · CNA · 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).CNA ↗
- Before
- not recorded
- After
- 2.3 (CVSS 4.0 · CNA · 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)
- Catalogue recordCVE added to the BlackTree catalogue.Official national cybersecurity authority ↗
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.