limbo.watch
Menu

In limbo for 596 days

GHSA-g58g-82mw-9m3p

RabbitMQ on Hex · published in rabbitmq/rabbitmq-server

Read the advisory on GitHub ↗

Fixed in 4.0.3. Dependabot, npm audit and OSV-Scanner won’t flag this yet. Find it in your project

Facts

Severity
Medium · CVSS score 6.1CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:L
Package name (RabbitMQ)
RabbitMQAs entered. Doesn’t look like a valid Hex package name, so scanners can’t match it. How to fix it
Affected versions (RabbitMQ)
>= 4.0.0, < 4.0.3As entered by the maintainer. Not reviewed.
Fixed in (RabbitMQ)
4.0.3
Package name (RabbitMQ)
RabbitMQAs entered. Doesn’t look like a valid Hex package name, so scanners can’t match it. How to fix it
Affected versions (RabbitMQ)
>= 3.13.0, < 3.13.8As entered by the maintainer. Not reviewed.
Fixed in (RabbitMQ)
3.13.8
CVE
CVE-2025-30219 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use RabbitMQ >= 4.0.0, < 4.0.3

Upgrade to 4.0.3 or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2025-03-25 21:14 UTC

    Published by the maintainers

    Cites CVE-2025-30219

  2. 2026-10-28 08:43 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-g58g-82mw-9m3p.json