VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

prosody: vulnerability history, versions and safety

prosody is a package in the Debian ecosystem. Vulert records 36 vulnerabilities for it across 37 releases, from Jun 2011 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded U36
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 01 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all prosody vulnerabilities

Vulert verdict on prosody i

Updated on 23 Oct 2026

Careful: 4 of the 36 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 36 vulnerabilities on record across 14 years, 4 in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 36 over 14 years · 4 in the last year i
  • Latest disclosure 01 May 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 4 i

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 holds for prosody, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 37 of 37 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 6
  • 2014 2
  • 2016 6
  • 2018 4
  • 2021 12
  • 2022 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for prosody

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Authentication Bypass Vulnerability in Prosody XMPP Server 8.8 high 0.10.2-1 30 Jul 2018
Remote Denial-of-Service Vulnerability in Prosody: Memory Exhaustion Risk 7.5 high 0.11.9-1 13 May 2021
Denial of Service Vulnerability in Prosody Due to LuaSocket Incompatibility 7.5 high 0.10.0-1 09 May 2018
Server Impersonation Risk in Prosody Due to Dialback Misconfiguration 7.5 high 0.11.9-1 13 May 2021
Uncontrolled CPU Consumption in Prosody: CVE-2021-32920 7.5 high 0.11.9-1 13 May 2021

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 prosody

Is prosody safe to use?

Vulert records 36 vulnerabilities for prosody in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does prosody have?

36 vulnerabilities are recorded for prosody in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new prosody vulnerabilities disclosed?

4 vulnerabilities were recorded for prosody in the last 12 months, and the oldest entry in this database dates to 22 Jun 2011. 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 prosody 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 prosody for upcoming vulnerabilities?

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