How severe is GHSA-42pc-678q-v8qj?

No CVSS score has been assigned to GHSA-42pc-678q-v8qj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-42pc-678q-v8qj?

GHSA-42pc-678q-v8qj affects the following packages: rabbitmq (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-42pc-678q-v8qj?

Update rabbitmq to 3.13.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42pc-678q-v8qj is resolved across your whole dependency graph.

How do I detect GHSA-42pc-678q-v8qj 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-42pc-678q-v8qj 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-42pc-678q-v8qj actively exploited in the wild?

No public exploit code has been indexed for GHSA-42pc-678q-v8qj 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-42pc-678q-v8qj?

GHSA-42pc-678q-v8qj has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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-42pc-678q-v8qj?

GHSA-42pc-678q-v8qj is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-42pc-678q-v8qj published, and has it been updated?

GHSA-42pc-678q-v8qj 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: Federation upstream skips vhost authorization…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% 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 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18, Federation upstream in RabbitMQ skips vhost authorization allowing cross-vhost message access. what the bug lets you do. A policymaker on one vhost reads and drains messages out of another vhost it has no permission on. With the default ack-mode the source messages are consumed (deleted), not copied. Why that should not 1. Federation validates the upstream URI without any vhost-access Cross-vhost message read/drain from a per-vhost policymaker, breaking vhost tenancy This issue is fixed in versions 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18.

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-42pc-678q-v8qj 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.

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 HatModerate

Product	Fixed in	Advisory
Red Hat Hardened Images	`rabbitmq-server4-3-main-4.3.6-1.hum1`	RHSA-2026:67552

Frequently Asked Questions

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18, Federation upstream in RabbitMQ skips vhost authorization allowing cross-vhost message access. what the bug lets you do. A policymaker on one vhost reads and drains messages out of another vhost it has no permission on. With the default ack-mode the source messages are consumed (deleted), not copied. Why that should not 1. Federation validates the upstream URI without any vhost-access Cross-vhost message read/drain from a per-vhost policymaker, breaking vhost tenancy This issue is fixed

O3 Security · Impact-Aware SCA

Is GHSA-42pc-678q-v8qj in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works

RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message accessGHSA-42pc-678q-v8qj