Ethical Hacking News
RabbitMQ has been hit with two critical access control-related flaws that could allow attackers to leak OAuth client secrets, expose enterprise messaging infrastructure to takeover risks, and bypass tenant boundaries. The discovery of these vulnerabilities marks another significant blow to the security landscape, highlighting the importance of staying vigilant in the ever-evolving world of cybersecurity.
RabbitMQ has been hit with two critical access control-related flaws. The first vulnerability (CVE-2026-57219) allows attackers to leak OAuth client secrets and gain full control over RabbitMQ installations. The second vulnerability (CVE-2026-57221) enables unauthorized users to enumerate queue and exchange names, read message counts, and bypass tenant boundaries. Both vulnerabilities have been addressed in the latest versions of RabbitMQ (4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15). Security experts recommend patching to the latest version, rotating OAuth client secrets, limiting access to port 15672, separating tenants by virtual host, and implementing firewall rules.
RabbitMQ, a popular message broker service used by many enterprises for its scalability and reliability, has recently been hit with two critical access control-related flaws that could allow attackers to leak OAuth client secrets, expose enterprise messaging infrastructure to takeover risks, and bypass tenant boundaries. The discovery of these vulnerabilities marks another significant blow to the security landscape, highlighting the importance of staying vigilant in the ever-evolving world of cybersecurity.
The first vulnerability, identified as CVE-2026-57219, is described as an obsolete HTTP API endpoint that reveals client secret on RabbitMQ installations that had OAuth 2 configured to use the management.oauth_client_secret configuration key. This allows an attacker to exchange it for an administrator token and obtain full control over every message, queue, user, and broker setting. Miggo's security team, which discovered and reported the flaw, pointed out that the risk is sharpest in cloud or multi-tenant setups, or where the management port is reachable by an untrusted network.
The second vulnerability, identified as CVE-2026-57221, is described as a missing authorization that allows any authenticated user who can connect to a virtual host to enumerate all queue and exchange names in that virtual host and read queue message counts and consumer counts, regardless of their actual permissions. Miggo's security team noted that the endpoint's authorization check was hard-coded to always allow the request, unlike every other sensitive management endpoint.
Both vulnerabilities have been addressed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15 of RabbitMQ. However, before the public disclosure of these vulnerabilities, there was no evidence of active exploitation of either one.
In addition to patching to the latest versions, security experts recommend rotating the OAuth client secret if the management interface is reachable over the internet, limiting access to port 15672 to prevent the management interface from being reachable over the network, separating tenants by virtual host, and implementing firewall rules to block access to the vulnerable endpoint on unpatched instances.
The disclosure of these vulnerabilities serves as a reminder that even the most seemingly secure systems can be vulnerable to exploitation. It highlights the importance of staying up-to-date with the latest patches and taking proactive measures to protect against potential threats.
Furthermore, this incident underscores the need for enterprises to implement robust security controls and monitoring mechanisms to detect and respond to such vulnerabilities quickly. This includes implementing a zero-trust architecture, regularly scanning for known vulnerabilities, and ensuring that access controls are enforced strictly across all systems and applications.
In conclusion, the recent discovery of critical flaws in RabbitMQ highlights the importance of staying vigilant in the world of cybersecurity. It serves as a reminder to patch software regularly, rotate sensitive data, and implement robust security measures to protect against potential threats.
Related Information:
https://www.ethicalhackingnews.com/articles/RabbitMQ-Flaws-Exposed-A-Threat-to-Enterprise-Messaging-Infrastructure-ehn.shtml
https://thehackernews.com/2026/07/rabbitmq-flaws-could-leak-oauth-secrets.html
https://nvd.nist.gov/vuln/detail/CVE-2026-57219
https://www.cvedetails.com/cve/CVE-2026-57219/
https://nvd.nist.gov/vuln/detail/CVE-2026-57221
https://www.cvedetails.com/cve/CVE-2026-57221/
Published: Wed Jul 15 03:22:52 2026 by llama3.2 3B Q4_K_M
