CVE-2008-2957

MEDIUMCVSS v2 · 6.46.4—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.4 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 2.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: EPSS, NVD CVSS v2.0
6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2.1%CVSS v2: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The UPnP functionality in Pidgin 2.0.0, and possibly other versions, allows remote attackers to trigger the download of arbitrary files and cause a denial of service (memory or disk consumption) via a UDP packet that specifies an arbitrary URL.

CVSS v2.0 (legacy)
6.4MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.4MEDIUMlow confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity64% × 45%
The EG Score, 6.4 of 10.
Exploitation2.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.1%
EPSS %ILE
81st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

July 1, 2008

Last Modified

April 23, 2026

References (11)

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupidgin (1:2.4.1-1ubuntu2.2) @ hardy2026-05-30ubuntu
redhatpidgin-0:2.5.2-6.el52008-12-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pidgin—
  • every version up to 2.4.3-4: fixed in 2.4.3-4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pidgin—
  • every version up to 2.4.3-4: fixed in 2.4.3-4
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pidgin—
  • every version up to 2.4.3-4: fixed in 2.4.3-4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pidgin—
  • every version up to 2.4.3-4: fixed in 2.4.3-4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 123 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:38 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  2. 2026-10-10 19:53 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  4. 2026-10-08 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  5. 2026-10-07 23:37 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  8. 2026-10-04 23:15 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  9. 2026-10-04 02:14 UTCOSV refresh
  10. 2026-10-03 14:20 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  11. 2026-10-01 19:42 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  12. 2026-09-30 14:57 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  13. 2026-09-29 07:50 UTCEG score recompute
  14. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  15. 2026-09-18 19:20 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  16. 2026-09-17 19:20 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  18. 2026-09-14 16:44 UTCOSV refresh
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  20. 2026-09-10 09:24 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  21. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  22. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  23. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  24. 2026-09-04 04:59 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  25. 2026-08-30 01:14 UTCEPSS rescoreEPSS 2.1% · 80th percentile
Show 59 more
  1. 2026-08-28 21:34 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  2. 2026-08-26 16:46 UTCOSV refresh
  3. 2026-08-15 01:24 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  4. 2026-08-10 06:39 UTCOSV refresh
  5. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  6. 2026-08-07 16:21 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  7. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  8. 2026-08-05 19:11 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  9. 2026-08-04 15:03 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  10. 2026-08-03 10:28 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  11. 2026-07-30 01:25 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  12. 2026-07-26 13:35 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
  13. 2026-07-25 14:12 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  14. 2026-07-25 07:11 UTCOSV refresh
  15. 2026-07-24 14:12 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  16. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  17. 2026-07-23 00:56 UTCEG score recompute
  18. 2026-07-23 00:35 UTCEG score recompute
  19. 2026-07-23 00:01 UTCEG score recompute
  20. 2026-07-22 21:40 UTCEG score recompute
  21. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  22. 2026-07-18 09:59 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  23. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  24. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  25. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  26. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  27. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  28. 2026-07-09 19:04 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  29. 2026-07-08 15:09 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  30. 2026-07-08 01:57 UTCOSV refresh
  31. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  32. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  33. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  34. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  35. 2026-07-02 14:00 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  36. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  37. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  38. 2026-06-29 14:02 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  39. 2026-06-28 14:03 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  40. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  41. 2026-06-27 03:04 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  42. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  43. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  44. 2026-06-23 21:29 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  45. 2026-06-22 14:22 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  46. 2026-06-21 14:53 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  47. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  48. 2026-06-19 13:55 UTCOSV refresh
  49. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  50. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  51. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  52. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.1% · 79th percentile
  53. 2026-06-14 23:13 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  54. 2026-06-13 22:57 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  55. 2026-06-12 23:08 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  56. 2026-06-11 13:56 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  57. 2026-06-10 22:14 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  58. 2026-06-10 13:17 UTCEPSS rescoreEPSS 1.7% · 82nd percentile
  59. 2026-06-08 14:13 UTCEPSS rescoreEPSS 1.7% · 82nd percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2008-2957?
CVE-2008-2957 is a medium-severity vulnerability; its CVE record was published on July 1, 2008. The UPnP functionality in Pidgin 2.0.0, and possibly other versions, allows remote attackers to trigger the download of arbitrary files and cause a denial of service (memory or disk consumption) via a UDP packet that specifies an arbitrary URL.
When was CVE-2008-2957 made public?
CVE-2008-2957 was made public on July 1, 2008: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 1, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-2957 actively exploited?
CVE-2008-2957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (81st percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-2957?
A fix for CVE-2008-2957 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-2957

Explore →

Is Your Infrastructure Affected by CVE-2008-2957?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs