CVE-2009-3026 json
protocols/jabber/auth.c in libpurple in Pidgin 2.6.0, and possibly other versions, does not follow the "require TLS/SSL" preference when co…
published 2009-08-31 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3010
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
protocols/jabber/auth.c in libpurple in Pidgin 2.6.0, and possibly other versions, does not follow the "require TLS/SSL" preference when connecting to older Jabber servers that do not follow the XMPP specification, which causes libpurple to connect to the server without the expected encryption and allows remote attackers to sniff sessions.
Patch / fix
- pidgin Debian 14, Debian 13, Debian 12 2.6.1-1
debian advisories DEBIAN-CVE-2009-3026
- pidgin RHEL 4 2.6.2-2.el4
- pidgin RHEL 5 PRODUCTIVITY, RHEL 5 2.6.2-2.el5
- finch RHEL 4 2.6.2-2.el4
- finch RHEL 5 PRODUCTIVITY, RHEL 5 2.6.2-2.el5
- libpurple RHEL 4 2.6.2-2.el4
- libpurple RHEL 5 PRODUCTIVITY, RHEL 5 2.6.2-2.el5
- pidgin-perl RHEL 4 2.6.2-2.el4
- pidgin-perl RHEL 5 PRODUCTIVITY, RHEL 5 2.6.2-2.el5
red hat advisories RHSA-2009:1453
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-3026 updated cvss 4.3
pidgin: ignores SSL/TLS requirements with old jabber servers
-
Red Hat Enterprise Linux AS version 4 finch 2.6.2-2.el4, pidgin 2.6.2-2.el4, libpurple 2.6.2-2.el4, pidgin-perl 2.6.2-2.el4, libpurple-tcl 2.6.2-2.el4, libpurple-perl 2.6.2-2.el4 Red Hat Enterprise Linux Desktop (v. 5 client) finch 2.6.2-2.el5, pidgin 2.6.2-2.el5, libpurple 2.6.2-2.el5, pidgin-perl 2.6.2-2.el5, libpurple-tcl 2.6.2-2.el5, libpurple-perl 2.6.2-2.el5 Red Hat Enterprise Linux Desktop version 4 finch 2.6.2-2.el4, pidgin 2.6.2-2.el4, libpurple 2.6.2-2.el4, pidgin-perl 2.6.2-2.el4, libpurple-tcl 2.6.2-2.el4, libpurple-perl 2.6.2-2.el4 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) finch 2.6.2-2.el5, pidgin 2.6.2-2.el5, libpurple 2.6.2-2.el5, pidgin-perl 2.6.2-2.el5, libpurple-tcl 2.6.2-2.el5, libpurple-perl 2.6.2-2.el5 Red Hat Enterprise Linux ES version 4 finch 2.6.2-2.el4, pidgin 2.6.2-2.el4, libpurple 2.6.2-2.el4, pidgin-perl 2.6.2-2.el4, libpurple-tcl 2.6.2-2.el4, libpurple-perl 2.6.2-2.el4 Red Hat Enterprise Linux Optional Productivity Applications (v. 5 server) finch 2.6.2-2.el5, pidgin 2.6.2-2.el5, libpurple 2.6.2-2.el5, pidgin-perl 2.6.2-2.el5, libpurple-tcl 2.6.2-2.el5, libpurple-perl 2.6.2-2.el5fixed: vendor fix RHSA-2009:1453
+1 more productsfewer
Red Hat Enterprise Linux WS version 4 finch 2.6.2-2.el4, pidgin 2.6.2-2.el4, libpurple 2.6.2-2.el4, pidgin-perl 2.6.2-2.el4, libpurple-tcl 2.6.2-2.el4, libpurple-perl 2.6.2-2.el4
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
developer.pidgin.im
/viewmtn/revision/diff/312e056d702d29379ea61aea9d27765f127bc888/with/55897c4ce0787edc1e7721b7f4a9b5cbc8357279
patch
-
securityfocus.com
/bid/36368
vdb-entry
- developer.pidgin.im /ticket/8131
-
secunia.com
/advisories/37071
third-party-advisory
-
openwall.com
/lists/oss-security/2009/08/24/2
mailing-list
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=542891
-
exchange.xforce.ibmcloud.com
/vulnerabilities/53000
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5757
vdb-entry, signature
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11070
vdb-entry, signature
Sources
- CVE List CVE-2009-3026
- NVD CVE-2009-3026
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.