VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pidgin: vulnerability history, versions and safety

pidgin is a package in the Debian ecosystem. Vulert records 160 vulnerabilities for it across 17 releases, from Oct 2007 to Jun 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
160 vulnerabilities recorded U160
i
5 with no fix published

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

See the unfixed vulnerabilities →
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 pidgin vulnerabilities

Vulert verdict on pidgin i

Updated on 23 Oct 2026

Careful: 5 of the 160 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 160 vulnerabilities on record across 14 years, none in the last year.

What to do: Plan around the 5 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 160 over 14 years · 0 in the last year i
  • Latest disclosure 02 Jun 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 5 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 pidgin, 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 17 of 17 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 4
  • 2008 10
  • 2009 26
  • 2010 14
  • 2011 16
  • 2012 12
  • 2013 8
  • 2014 32
  • 2017 32
  • 2018 3
  • 2019 2
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for pidgin

The 5 most severe of 160 vulnerabilities recorded for this package

Search all 160 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Code Execution Vulnerability in Pidgin 9.8 critical 2.11.0-1 05 Sep 2018
Out-of-Bounds Write Vulnerability in Pidgin MXIT Protocol Handling 8.1 high 2.11.0-1 06 Jan 2017
Buffer Overflow Vulnerability in Pidgin MXIT Protocol Handling 8.1 high 2.11.0-1 06 Jan 2017
Memory Corruption Vulnerability in Pidgin MXIT Protocol Handling 8.1 high 2.11.0-1 06 Jan 2017
Critical Memory Corruption Vulnerability in Pidgin: CVE-2016-2368 8.1 high 2.11.0-1 06 Jan 2017

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 pidgin

Is pidgin safe to use?

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

How many vulnerabilities does pidgin have?

160 vulnerabilities are recorded for pidgin in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 160 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 pidgin vulnerabilities disclosed?

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

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