How severe is GHSA-4r6f-9cpw-f6g6?

No CVSS score has been assigned to GHSA-4r6f-9cpw-f6g6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4r6f-9cpw-f6g6?

GHSA-4r6f-9cpw-f6g6 affects the following packages: rabbitmq (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-4r6f-9cpw-f6g6?

Update rabbitmq to 3.13.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r6f-9cpw-f6g6 is resolved across your whole dependency graph.

How do I detect GHSA-4r6f-9cpw-f6g6 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rabbitmq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4r6f-9cpw-f6g6 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-4r6f-9cpw-f6g6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4r6f-9cpw-f6g6 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-4r6f-9cpw-f6g6?

GHSA-4r6f-9cpw-f6g6 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-4r6f-9cpw-f6g6?

GHSA-4r6f-9cpw-f6g6 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4r6f-9cpw-f6g6 published, and has it been updated?

GHSA-4r6f-9cpw-f6g6 was published on October 1, 2026 and was last updated on October 1, 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: Web MQTT with PROXY Protocol enabled: a…

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

📦rabbitmq

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`rabbitmq`	≥ 3.13.0&&< 3.13.18	3.13.18

Affected Products

1 product · 5 configurations

Application

rabbitmq serverbroadcom

≥ 4.3.0 && < 4.3.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rabbitmq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rabbitmq to 3.13.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r6f-9cpw-f6g6 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.1

O3 Security · Impact-Aware SCA

Is GHSA-4r6f-9cpw-f6g6 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works

RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypassGHSA-4r6f-9cpw-f6g6