CVE-2026-67223

Analyzed Analyzed - Analysis Complete

LDAP Injection in RabbitMQ Auth Backend

Publication date: 2026-09-25

Last updated on: 2026-10-15

Assigner: GitHub, Inc.

Description

RabbitMQ is a messaging and streaming broker. The advisory establishes affected 3.13, 4.0, 4.1, 4.2, and 4.3 maintenance lines but contains conflicting first-fixed versions for the 3.13, 4.0, and 4.1 lines. fill/2 substitutes ${username} into user_dn_pattern without RFC 4514 DN escaping, allowing a crafted username to alter the LDAP bind DN and potentially select a different directory entry. Exploitation requires rabbitmq_auth_backend_ldap with a user_dn_pattern containing ${username}, a directory layout in which the injected suffix resolves usefully, and a password valid for the resulting DN. The advisory body identifies 3.13.15, 4.0.20, 4.1.11, 4.2.9, and 4.3.3 as fixed, while structured metadata identifies 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3. No fixed-version assertion is certifiable until a curator resolves this conflict.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-10-15

Generated

2026-10-16

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-14

NVD

CVE-2026-67223

EUVD

EUVD-2026-87156

Affected Vendors & Products

Vendor	Product	Version / Range
broadcom	rabbitmq_server	From 4.1.0 (inc) to 4.1.14 (exc)
broadcom	rabbitmq_server	From 4.2.0 (inc) to 4.2.9 (exc)
broadcom	rabbitmq_server	From 4.3.0 (inc) to 4.3.3 (exc)
broadcom	rabbitmq_server	From 4.0.0 (inc) to 4.0.23 (exc)
broadcom	rabbitmq_server	From 3.13.0 (inc) to 3.13.18 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-90	The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

Attack-Flow Graph

Executive Summary

RabbitMQ is affected by an LDAP injection vulnerability where the ${username} placeholder in user_dn_pattern is not properly escaped. This allows an attacker to manipulate the LDAP bind DN by crafting a malicious username, potentially bypassing authentication or accessing unauthorized directory entries.

Detection Guidance

To detect CVE-2026-67223, check if RabbitMQ is running with rabbitmq_auth_backend_ldap enabled and a user_dn_pattern containing ${username}. Review LDAP bind logs for unusual DNs or failed authentication attempts that may indicate exploitation attempts.

Impact Analysis

If exploited, this vulnerability could allow unauthorized access to RabbitMQ instances using LDAP authentication. Attackers might impersonate other users, gain elevated privileges, or access sensitive data depending on the LDAP directory structure.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating GDPR's integrity and confidentiality principles or HIPAA's access control requirements. Organizations using affected RabbitMQ versions with LDAP may face compliance violations and potential fines.

Mitigation Strategies

Disable rabbitmq_auth_backend_ldap if not required. If using LDAP, ensure user_dn_pattern does not contain ${username} or apply RFC 4514 DN escaping. Upgrade to fixed versions if available: 3.13.15/3.13.18, 4.0.20/4.0.23, 4.1.11/4.1.14, 4.2.9, or 4.3.3.

Hi! I’m here to help you understand CVE-2026-67223. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70