Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

jabberd vulnerabilities and fixes

Recent CVEs affecting jabberd, with upgrade or downgrade steps. 2 tracked.

jabberd has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2006-03-21. Highest priority: CVE-2006-1329 (score 39/100).

FAQ

How do I fix jabberd vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is jabberd being exploited right now?

None of the tracked jabberd CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which jabberd CVE should I patch first?

CVE-2006-1329 currently ranks highest (39/100): The SASL negotiation in Jabber Studio jabberd before 2.0s11 allows remote attackers to cause a denial of servi.

← Back to latest CVEs