PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-67410 – OAuth2 Client Secret Disclosure – RabbitMQ Management (4.2.0–4.2.8, 4.3.0–4.3.2)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-67410 is an information-disclosure vulnerability in the RabbitMQ Management UI that exposes a configured OAuth2 client secret to unauthenticated users. When OAuth2 authentication is enabled for the Management UI and the configured flow/identity provider uses a client secret, that secret is embedded in JavaScript served from an unauthenticated endpoint. The issue carries a CVSS score of 8.2 (High) and affects RabbitMQ 4.2.0–4.2.8 and 4.3.0–4.3.2.

Technical details

  • Root cause: the /js/oidc-oauth/bootstrap.js endpoint, handled by rabbit_mgmt_oauth_bootstrap, embeds the oauth_client_secret configuration value directly into the JavaScript it returns, and fails to implement an authorization check (Cowboy REST’s authorization callback is not enforced) before serving that response.
  • Trigger conditions: OAuth2 authentication must be enabled for the RabbitMQ Management UI, and the configured OAuth2 flow/identity provider must use a client secret.
  • Attack vector: network — any client able to reach the Management UI HTTP port can request the endpoint without providing credentials.
  • Impact: disclosure of the OAuth2 client secret allows an attacker to complete or hijack the OAuth2 authorization code flow (e.g., exchange stolen authorization codes for access tokens), potentially impersonating the RabbitMQ Management UI to the identity provider and gaining unauthorized access to protected resources.

Affected software

  • RabbitMQ (rabbitmq-server) 4.2.0 through 4.2.8 (inclusive)
  • RabbitMQ (rabbitmq-server) 4.3.0 through 4.3.2 (inclusive)
  • Only deployments with the Management UI enabled, OAuth2 authentication active, and a configured OAuth2 client secret are affected

Severity

  • CVSS Score: 8.2 (High)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: upgrade RabbitMQ to version 4.2.9 or 4.3.3, which fix the unauthenticated exposure of the client secret.
  • If unable to patch immediately:
    • Switch to an OAuth2 flow that does not require a client secret (e.g., PKCE-based public client flows).
    • Disable the rabbitmq_auth_backend_oauth2 plugin and use an alternative authentication backend until patched.
    • Alternatively, disable the rabbitmq_management plugin and rely on other monitoring (e.g., Prometheus) until the upgrade can be applied.
    • Rotate any OAuth2 client secret that may have been exposed, regardless of mitigation path chosen.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge