dbcve.org
Rabbitmq ServerApplication · Broadcom

CVE-2026-57219

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 4.2.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured with management.oauth_client_secret, exposing credentials to unauthenticated callers when the management plugin and that OAuth configuration are enabled. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The obsolete GET /api/auth endpoint in RabbitMQ exposes the OAuth 2 client secret (management.oauth_client_secret) to unauthenticated callers when the management plugin with OAuth configuration is enabled. This credential disclosure allows attackers to potentially obtain valid OAuth credentials for further attacks.

MitigationUpgrade RabbitMQ to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later to patch the vulnerable endpoint. Until upgrade is possible, disable the management plugin or ensure the management.oauth_client_secret configuration is not in use.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rabbitmq ServerApplication
Affected:>= 3.13.0, < 4.2.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check RabbitMQ server version
    Run `rabbitmqctl version` or `rabbitmqctl status` and locate the version string in the output
    Affected if Version is 3.13.0 or higher but lower than 4.2.6
  2. Verify management plugin is enabled
    Run `rabbitmqctl list_plugins` and confirm the management plugin shows as enabled
    Affected if The management plugin is listed as enabled (marked with [E])
  3. Inspect for OAuth client secret configuration
    Examine the RabbitMQ configuration files (rabbitmq.conf, advanced.config, or conf.d/*.conf) for the setting `management.oauth_client_secret`
    Affected if The configuration contains a management.oauth_client_secret value (regardless of its content)
  4. Test unauthenticated access to /api/auth endpoint
    Send a GET request to the management plugin endpoint: `curl -s http://localhost:15672/api/auth` (or the configured management port) without providing any authentication credentials
    Affected if The endpoint responds with any HTTP 200 or 401 (meaning it's accessible without authentication) and potentially exposes the OAuth client secret in the response body

User is affected if RabbitMQ version is in the range 3.13.0 to 4.2.5, the management plugin is enabled, OAuth configuration with management.oauth_client_secret is present, and the /api/auth endpoint responds to unauthenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.6 or later
Fixed in 4.2.6
Vendor patch github.com →
Interim mitigation

Upgrade RabbitMQ to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later to patch the vulnerable endpoint. Until upgrade is possible, disable the management plugin or ensure the management.oauth_client_secret configuration is not in use.

Recommended fix High confidence

Upgrade to RabbitMQ Server 3.13.15, 4.0.20, 4.1.11, or 4.2.6 depending on your current major version branch

  1. 1. Identify current RabbitMQ server version using 'rabbitmq-diagnostics status' or checking package manager
  2. 2. Determine appropriate upgrade target based on current version branch (3.13.x -> 3.13.15, 4.0.x -> 4.0.20, 4.1.x -> 4.1.11, 4.2.x -> 4.2.6)
  3. 3. Backup RabbitMQ configuration files (rabbitmq.conf, advanced.conf, enabled plugins)
  4. 4. Stop RabbitMQ service before upgrade
  5. 5. Upgrade RabbitMQ Server to the appropriate fixed version via package manager or binary release
  6. 6. Start RabbitMQ service after upgrade completes
  7. 7. Verify the fix by confirming the GET /api/auth endpoint no longer returns the OAuth client secret
  8. 8. If using management.oauth_client_secret, verify OAuth authentication still functions correctly
Caveat Review release notes for your version branch to check for any breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rabbitmq Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57219 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data