VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

rabbit_common: vulnerability history, versions and safety

rabbit_common is a package in the Hex ecosystem. Vulert records 4 vulnerabilities for it across 13 releases, from May 2022 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M2 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 30 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rabbit_common vulnerabilities

Vulert verdict on rabbit_common 4.3.4 i

Updated on 23 Oct 2026

Good news: 4.3.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 94/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 4.3.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.4 — unaffected i
  • Vulnerabilities on record 4 over 4 years · 2 in the last year i
  • Latest disclosure 30 Jun 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 18,654,590 packages i
  • Last release 2 months ago i

Version list, release dates, licence and dependants published by hex.pm, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for rabbit_common, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.3.4 28 Jul 2026 none — — Details →
4.2.1 06 Nov 2025 none — — Details →
4.2.0 06 Nov 2025 none — — Details →
4.2.0-rc.1 06 Nov 2025 none — — Details →
4.1.6 06 Nov 2025 none — — Details →
4.1.5 06 Nov 2025 none — — Details →
4.1.5-rc.2 06 Nov 2025 none — — Details →
4.1.5-rc.1 06 Nov 2025 none — — Details →
4.0.3 28 Oct 2024 none — — Details →
4.0.3-rc.1 25 Oct 2024 none — — Details →
4.0.2 19 Sep 2024 none — — Details →
4.0.2-rc.2 19 Sep 2024 none — — Details →
4.0.2-rc.1 19 Sep 2024 none — — Details →
4.0.1 18 Sep 2024 none — — Details →
4.0.0 18 Sep 2024 none — — Details →
4.0.0-rc.2 17 Sep 2024 none — — Details →
4.0.0-rc.1 11 Sep 2024 none — — Details →
3.13.7 26 Aug 2024 none — — Details →
3.13.6 23 Jul 2024 none — — Details →
3.13.5 20 Jul 2024 none — — Details →
3.13.4 03 Jul 2024 none — — Details →
3.13.3 31 May 2024 none — — Details →
3.13.2 30 Apr 2024 none — — Details →
3.13.2-rc.1 30 Apr 2024 none — — Details →
3.13.1 29 Mar 2024 none — — Details →
3.13.0 22 Feb 2024 none — — Details →
3.13.0-rc.6 22 Feb 2024 none — — Details →
3.13.0-rc.5 14 Feb 2024 none — — Details →
3.13.0-rc.4 04 Jan 2024 none — — Details →
3.13.0-rc.3 18 Dec 2023 none — — Details →
3.13.0-rc.2 31 Oct 2023 none — — Details →
3.13.0-rc.1 19 Oct 2023 none — — Details →
3.12.14 05 May 2024 none — — Details →
3.12.13 16 Feb 2024 none — — Details →
3.12.12 04 Jan 2024 none — — Details →
3.12.11 21 Dec 2023 none — — Details →
3.12.10 22 Nov 2023 H1 — Yes Details →
3.12.9 17 Nov 2023 H1 — Yes Details →
3.12.8 31 Oct 2023 H1 — Yes Details →
3.12.7 17 Oct 2023 H1 — Yes Details →
3.12.6 21 Sep 2023 M1 — Yes Details →
3.12.5 21 Sep 2023 M1 — Yes Details →
3.12.4 24 Aug 2023 M1 — Yes Details →
3.12.3 17 Aug 2023 M1 — Yes Details →
3.12.2 17 Jul 2023 M1 — Yes Details →
3.12.1 26 Jun 2023 M1 — Yes Details →
3.12.0 01 Jun 2023 M1 — Yes Details →
3.12.0-rc.4 30 May 2023 none — — Details →
3.12.0-rc.3 20 May 2023 none — — Details →
3.12.0-rc.2 13 May 2023 none — — Details →
3.12.0-rc.1 26 Apr 2023 none — — Details →
3.11.28 21 Dec 2023 none — — Details →
3.11.27 13 Dec 2023 none — — Details →
3.11.26 21 Nov 2023 none — — Details →
3.11.25 31 Oct 2023 none — — Details →
3.11.24 17 Oct 2023 none — — Details →
3.11.23 11 Sep 2023 none — — Details →
3.11.22 24 Aug 2023 none — — Details →
3.11.21 17 Aug 2023 none — — Details →
3.11.20 17 Jul 2023 none — — Details →
3.11.19 26 Jun 2023 none — — Details →
3.11.18 05 Jun 2023 none — — Details →
3.11.17 29 May 2023 none — — Details →
3.11.16 13 May 2023 none — — Details →
3.11.15 29 Apr 2023 none — — Details →
3.11.14 27 Apr 2023 none — — Details →
3.11.13 31 Mar 2023 none — — Details →
3.11.12 30 Mar 2023 none — — Details →
3.11.11 20 Mar 2023 none — — Details →
3.11.10 02 Mar 2023 none — — Details →
3.11.9 12 Feb 2023 none — — Details →
3.11.8 30 Jan 2023 none — — Details →
3.11.7 17 Jan 2023 none — — Details →
3.11.6 05 Jan 2023 none — — Details →
3.11.5 13 Dec 2022 none — — Details →
3.11.4 28 Nov 2022 none — — Details →
3.11.3 09 Nov 2022 none — — Details →
3.11.2 18 Oct 2022 none — — Details →
3.11.1 13 Oct 2022 none — — Details →
3.11.0 26 Sep 2022 none — — Details →
3.11.0-rc.2 21 Sep 2022 none — — Details →
3.11.0-rc.1 03 Sep 2022 none — — Details →
3.11.0-1 29 Sep 2022 none — — Details →
3.10.25 18 Jul 2023 none — — Details →
3.10.24 05 Jun 2023 none — — Details →
3.10.23 24 May 2023 none — — Details →
3.10.22 29 Apr 2023 none — — Details →
3.10.21 27 Apr 2023 none — — Details →
3.10.20 22 Mar 2023 none — — Details →
3.10.19 02 Mar 2023 none — — Details →
3.10.18 12 Feb 2023 none — — Details →
3.10.17 31 Jan 2023 none — — Details →
3.10.16 30 Jan 2023 none — — Details →
3.10.15 30 Jan 2023 none — — Details →
3.10.14 16 Jan 2023 none — — Details →
3.10.13 13 Dec 2022 none — — Details →
3.10.12 28 Nov 2022 none — — Details →
3.10.11 09 Nov 2022 none — — Details →
3.10.10 18 Oct 2022 none — — Details →
3.10.9 12 Oct 2022 none — — Details →
3.10.8 23 Sep 2022 none — — Details →
3.10.7 02 Aug 2022 none — — Details →
3.10.6 10 Jul 2022 none — — Details →
3.10.5 01 Jun 2022 none — — Details →
3.10.4 31 May 2022 none — — Details →
3.10.3 31 May 2022 none — — Details →
3.10.2 20 May 2022 none — — Details →
3.10.1 10 May 2022 M1 — Yes Details →
3.10.0 03 May 2022 M1 — Yes Details →
3.10.0-rc.6 30 Apr 2022 none — — Details →
3.10.0-rc.5 28 Apr 2022 none — — Details →
3.9.29 09 Mar 2023 none — — Details →
3.9.28 30 Jan 2023 none — — Details →
3.9.27 13 Dec 2022 none — — Details →
3.9.26 28 Nov 2022 none — — Details →
3.9.25 09 Nov 2022 none — — Details →
3.9.24 18 Oct 2022 none — — Details →
3.9.23 22 Sep 2022 none — — Details →
3.9.22 01 Aug 2022 none — — Details →
3.9.21 09 Jul 2022 none — — Details →

The newest 120 of 280 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rabbit_common

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-51988: rabbit_common Package - Insufficient Permission Verification in Queue Deletion Endpoint 6.5 high 3.12.11 06 Nov 2024
CVE-2022-31008: rabbit_common Package Suffers from Predictable Credential Obfuscation in Shovel and Federation Plugins 5.5 medium 3.10.2 30 Jun 2026
CVE-2023-46118: rabbit_common Denial of Service via Large HTTP API Messages 4.9 medium 3.12.7 30 Jun 2026
CVE-2019-11291: Cross-site Scripting in RabbitMQ 3.5 low 3.7.20 24 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rabbit_common

Is rabbit_common safe to use?

Vulert records 4 vulnerabilities for rabbit_common in Hex: 0 critical, 1 high, 2 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rabbit_common's Vulert package health score?

Vulert scores rabbit_common 94/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of rabbit_common affected?

No. 4.3.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does rabbit_common have?

4 vulnerabilities are recorded for rabbit_common in the Hex ecosystem: 0 critical, 1 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rabbit_common vulnerabilities disclosed?

2 vulnerabilities were recorded for rabbit_common in the last 12 months, and the oldest entry in this database dates to 24 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rabbit_common are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rabbit_common for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rabbit_common version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.