Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💧 Hex

GHSA-w6cq-9cf4-gqpg

MEDIUM

RabbitMQ vulnerable to Denial of Service by publishing large messages over the HTTP API

Also known asBIT-rabbitmq-2023-46118CVE-2023-46118
Published
Jun 30, 2026
Updated
Jun 30, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
💧rabbit_common💧rabbit_common

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

Description

Summary

Responsibly disclosed by @NSEcho.

HTTP API did not enforce an HTTP request body limit, making it vulnerable for DoS attacks with very large messages.

Details

An authenticated user with sufficient credentials can publish a very large messages over the HTTP API and cause target node to be terminated by an "out-of-memory killer"-like mechanism.

A PoC was provided to Team RabbitMQ privately.

Impact

Denial of Service

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
💧Hexrabbit_common3.12.0&&< 3.12.73.12.7
💧Hexrabbit_common3.11.0&&< 3.11.243.11.24

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rabbit_common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update rabbit_common to 3.12.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w6cq-9cf4-gqpg is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-w6cq-9cf4-gqpg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w6cq-9cf4-gqpg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Responsibly disclosed by @NSEcho. HTTP API did not enforce an HTTP request body limit, making it vulnerable for DoS attacks with very large messages. ### Details An authenticated user with sufficient credentials can publish a very large messages over the HTTP API and cause target node to be terminated by an "out-of-memory killer"-like mechanism. A PoC was provided to Team RabbitMQ privately. ### Impact Denial of Service
O3 Security · Impact-Aware SCA

Is GHSA-w6cq-9cf4-gqpg in your dependencies?

O3 detects GHSA-w6cq-9cf4-gqpg across Hex dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.