VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

ejabberd: vulnerability history, versions and safety

ejabberd is a package in the Hex ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ejabberd vulnerabilities

Vulert verdict on ejabberd 26.9.0 i

Updated on 23 Oct 2026

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

Package health score 100/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 26.9.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 48,696 packages i
  • Last release this month 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 ejabberd, 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
26.9.0 05 Oct 2026 none — — Details →
26.7.0 30 Jul 2026 none — — Details →
26.4.0 20 Apr 2026 none — — Details →
26.3.0 25 Mar 2026 none — — Details →
26.2.0 11 Feb 2026 none — — Details →
26.1.0 21 Jan 2026 none — — Details →
25.10.0 29 Oct 2025 none — — Details →
25.8.0 22 Aug 2025 none — — Details →
25.7.0 11 Jul 2025 none — — Details →
25.4.0 16 Apr 2025 none — — Details →
25.3.0 28 Mar 2025 none — — Details →
24.12.0 19 Dec 2024 none — — Details →
24.10.0 29 Oct 2024 none — — Details →
24.7.0 19 Jul 2024 none — — Details →
24.6.0 01 Jul 2024 none — — Details →
24.2.6 28 Feb 2024 none — — Details →
23.10.0 19 Oct 2023 none — — Details →
23.4.0 21 Apr 2023 none — — Details →
23.1.0 17 Jan 2023 none — — Details →
22.10.0 28 Oct 2022 none — — Details →
22.5.0 12 May 2022 none — — Details →
21.12.0 09 Dec 2021 none — — Details →
21.7.0 26 Jul 2021 none — — Details →
21.4.0 08 Apr 2021 none — — Details →
21.1.0 29 Jan 2021 none — — Details →
20.12.0 17 Dec 2020 none — — Details →
20.7.0 30 Jul 2020 none — — Details →
20.4.0 30 Apr 2020 none — — Details →
20.3.0 26 Mar 2020 none — — Details →
20.2.0 26 Feb 2020 none — — Details →
20.1.0 18 Feb 2020 none — — Details →
19.9.1 21 Oct 2019 none — — Details →
19.9.0 30 Sep 2019 none — — Details →
19.8.0 06 Aug 2019 none — — Details →
19.5.0 05 Jun 2019 none — — Details →
19.2.0 01 Mar 2019 none — — Details →
18.12.1 26 Dec 2018 none — — Details →
18.12.0 26 Dec 2018 none — — Details →
18.6.0 29 Jun 2018 none — — Details →
18.4.0 07 May 2018 none — — Details →
18.3.0 06 Apr 2018 none — — Details →
18.1.0 22 Jan 2018 none — — Details →
17.11.0 29 Dec 2017 none — — Details →
17.9.0 16 Oct 2017 none — — Details →
17.6.0 06 Jul 2017 none — — Details →
17.3.0 27 Mar 2017 none — — Details →
17.1.0 23 Jan 2017 none — — Details →
16.12.0-beta1 01 Dec 2016 none — — Details →
16.9.0 25 Nov 2016 none — — Details →
16.8.0 08 Sep 2016 none — — Details →
16.6.2 08 Jul 2016 none — — Details →
16.6.1 08 Jul 2016 none — — Details →
16.6.0 30 Jun 2016 none — — Details →
16.4.1 10 Jun 2016 none — — Details →
16.4.0 31 May 2016 none — — Details →
16.3.0 30 Mar 2016 none — — Details →
16.2.0 29 Feb 2016 none — — Details →
16.1.0-beta1 08 Feb 2016 none — — Details →

All 58 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for ejabberd

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2011-4320: Ejabberd DoS via malformed stanza N/A medium 2.1.9 17 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 ejabberd

Is ejabberd safe to use?

Vulert records 1 vulnerabilities for ejabberd in Hex: 0 critical, 0 high, 1 medium and 0 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 ejabberd's Vulert package health score?

Vulert scores ejabberd 100/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 ejabberd affected?

No. 26.9.0, 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 ejabberd have?

1 vulnerability is recorded for ejabberd in the Hex ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ejabberd vulnerabilities disclosed?

0 vulnerabilities were recorded for ejabberd in the last 12 months, and the oldest entry in this database dates to 17 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 ejabberd 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 ejabberd for upcoming vulnerabilities?

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