How severe is GHSA-pj24-8j6m-vq9q?

No CVSS score has been assigned to GHSA-pj24-8j6m-vq9q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pj24-8j6m-vq9q?

Affected package information for GHSA-pj24-8j6m-vq9q is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-pj24-8j6m-vq9q?

Upgrade the affected component to the fixed release for GHSA-pj24-8j6m-vq9q, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-pj24-8j6m-vq9q in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-pj24-8j6m-vq9q if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-pj24-8j6m-vq9q actively exploited in the wild?

No public exploit code has been indexed for GHSA-pj24-8j6m-vq9q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pj24-8j6m-vq9q?

GHSA-pj24-8j6m-vq9q has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pj24-8j6m-vq9q?

GHSA-pj24-8j6m-vq9q is classified as Information Exposure (CWE-200), CWE-522 (CWE-522). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-pj24-8j6m-vq9q?

A Nuclei detection template exists for GHSA-pj24-8j6m-vq9q, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-pj24-8j6m-vq9q published, and has it been updated?

GHSA-pj24-8j6m-vq9q was published on July 10, 2026 and was last updated on September 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

RabbitMQ: Unauthenticated disclosure of OAuth client…

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pj24-8j6m-vq9q.

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk+0.85%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

1 product · 1 configurations

Application

rabbitmq serverbroadcom

≥ 3.13.0 && < 4.2.6

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-pj24-8j6m-vq9q, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

How to detect GHSA-pj24-8j6m-vq9q

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-pj24-8j6m-vq9q -u https://target

Template: RabbitMQ Management - OAuth 2 Client Secret Disclosure
Severity: high
Impact: Unauthenticated attackers can access OAuth 2 client secrets, leading to credential exposure and potential unauthorized access.
Remediation: Update to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later.

Template by ProjectDiscovery nuclei-templates (aryu-ru), MIT licensed. View the full template. Scan only systems you are authorised to test.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Hardened Images	`rabbitmq-server4-3-main-4.3.2-1.hum1`	RHSA-2026:35939
Red Hat Hardened Images	`rabbitmq-server4-2-main-4.2.8-1.hum1`	RHSA-2026:35940

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-pj24-8j6m-vq9q in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurationsGHSA-pj24-8j6m-vq9q