CVSS 4.0
6.3 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NMedium (6.3) in broadcom rabbitmq server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExplain CVE-2026-67242 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67242?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67242?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67242 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| broadcom:rabbitmq_server | from 4.2.0 before 4.2.9 |
| broadcom:rabbitmq_server | from 4.3.0 before 4.3.3 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | rabbitmq-server | 4.3.6-1 | DEBIAN-CVE-2026-67242 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 26.04:LTS and 4 more | rabbitmq-server | no fix listed | UBUNTU-CVE-2026-67242 |
| Red Hat | hummingbird:1 | rabbitmq-server4.3 | 0:4.3.6-1.hum1 | RHSA-2026:67552 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.
Red Hat rates this Moderate.
Moderate severity is assigned to this flaw because successful exploitation requires multiple non-default preconditions, including an unconventional Identity Provider setup and an attacker already holding a legitimately signed credential. In typical Red Hat environments, RabbitMQ relies on standard internal authentication or Identity Providers that issue token expiration values strictly as integer timestamps rather than floating-point numbers. Consequently, the absence of expiration enforcement only affects deployments explicitly integrated with third-party token issuers that provide fractional NumericDate timestamps, limiting the overall attack surface.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | rabbitmq-server4-3-main-4.3.6-1.hum1 | Fixed 2026-09-15 | RHSA-2026:67552 |
| Red Hat Hardened Images | rabbitmq-server4.2 | Will not fix | |
| Red Hat OpenStack Platform 13 (Queens) | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 16.2 | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 17.1 | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 18.0 | rabbitmq-server | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67242.