RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-295.
Summary
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, When no CA bundle is available, ssl_options/1 falls back to [{verify, verify_none}] with no warning. An attacker in a man-in-the-middle position can forge the JWKS response, which leads the broker to accept arbitrary JWTs. Preconditions include The OAuth2 plugin must be in use with no cacertfile configured and the OS CA bundle empty or unreadable (for example, in a minimal container), and the attacker must hold a network man-in-the-middle position.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| rabbitmq | rabbitmq-server | 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 | 3.13.15, 4.0.20, 4.1.11, 4.2.6 | Patch available | CNA |
- rabbitmq-server Vendorrabbitmq Affected 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* | 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 | Vulnerable | Broadcom |
- cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* Versions 3.13.0 to before 3.13.15; 4.0.0 to before 4.0.20; 4.1.0 to before 4.1.11; 4.2.0 to before 4.2.6 Vulnerable ·Broadcom
Remediation
- Fix · CNA rabbitmq-server (rabbitmq) Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6
Red Hat 1 advisory
- RHSA-2026:67552 Released 2026-09-15 · Red Hat rating ImportantRed Hat Hardened Images RPMs bug fix and enhancement update
- Red Hat Hardened Images rabbitmq-server4.3-4.3.6-1.hum1@aarch64, rabbitmq-server4.3-4.3.6-1.hum1@src, rabbitmq-server4.3-4.3.6-1.hum1@x86_64
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Hardened Images | Fixed | RHSA-2026:67552 |
Not affected: 5 products
- Red Hat Hardened Images
- Red Hat OpenStack Platform 13 (Queens)
- Red Hat OpenStack Platform 16.2
- Red Hat OpenStack Platform 17.1
- Red Hat OpenStack Platform 18.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-67404
- 2026-10-09 Fix available: RHSA-2026:67552 · Red Hat
- 2026-10-09 Fix available: Red Hat Hardened Images · Red Hat
- 2026-10-09 CVSS score added · Red Hat
- 2026-10-20 CVSS score added · NVD
References
More rabbitmq vulnerabilities
- TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
- TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
- TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
- TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
- TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
- TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
Sources
- CVE-2026-67404 · CVE Program
- CVE-2026-67404 · NVD
- FIRST EPSS
- CVE-2026-67404 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences