CVE-2008-0299

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/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. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
73.6%
KEV
Not listed

Published

January 16, 2008

Last Modified

April 23, 2026

References (24)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
paramiko0.1-bulbasaur ... 1.7.1 (24 versions)1.7.2—

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-23 00:55 UTCEG score recompute
  2. 2026-07-23 00:34 UTCEG score recompute
  3. 2026-07-23 00:00 UTCEG score recompute
  4. 2026-07-22 21:39 UTCEG score recompute
  5. 2026-07-22 14:03 UTCEPSS rescore
  6. 2026-07-21 15:19 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-18 09:59 UTCEPSS rescore
  9. 2026-07-16 16:58 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-15 01:55 UTCEPSS rescore
  13. 2026-07-13 06:07 UTCEPSS rescore
  14. 2026-07-11 08:22 UTCEPSS rescore
  15. 2026-07-08 15:09 UTCEPSS rescore
  16. 2026-07-08 05:57 UTCOSV refresh
  17. 2026-07-06 16:22 UTCEPSS rescore
  18. 2026-07-06 02:19 UTCEPSS rescore
  19. 2026-07-05 02:26 UTCEPSS rescore
  20. 2026-07-04 06:27 UTCEPSS rescore
  21. 2026-07-04 06:27 UTCEPSS rescore
  22. 2026-07-02 14:00 UTCEPSS rescore
  23. 2026-07-01 15:02 UTCEPSS rescore
  24. 2026-07-01 15:02 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEPSS rescore
Show 70 more
  1. 2026-06-30 23:19 UTCEPSS rescore
  2. 2026-06-29 14:02 UTCEPSS rescore
  3. 2026-06-29 14:02 UTCEPSS rescore
  4. 2026-06-28 14:03 UTCEPSS rescore
  5. 2026-06-28 04:52 UTCEPSS rescore
  6. 2026-06-27 03:04 UTCEPSS rescore
  7. 2026-06-25 13:46 UTCEPSS rescore
  8. 2026-06-25 13:46 UTCEPSS rescore
  9. 2026-06-24 14:02 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-21 14:53 UTCEPSS rescore
  14. 2026-06-19 19:22 UTCEPSS rescore
  15. 2026-06-19 19:22 UTCEPSS rescore
  16. 2026-06-19 17:55 UTCOSV refresh
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
  26. 2026-06-12 23:08 UTCEPSS rescore
  27. 2026-06-10 22:14 UTCEPSS rescore
  28. 2026-06-10 13:17 UTCEPSS rescore
  29. 2026-06-08 14:13 UTCEPSS rescore
  30. 2026-06-07 15:21 UTCEPSS rescore
  31. 2026-06-06 13:44 UTCEPSS rescore
  32. 2026-06-06 13:44 UTCEPSS rescore
  33. 2026-06-05 22:44 UTCEPSS rescore
  34. 2026-06-05 22:44 UTCEPSS rescore
  35. 2026-06-05 06:07 UTCEPSS rescore
  36. 2026-06-04 13:09 UTCEPSS rescore
  37. 2026-06-04 13:09 UTCEPSS rescore
  38. 2026-06-04 13:09 UTCEPSS rescore
  39. 2026-06-02 20:10 UTCEPSS rescore
  40. 2026-06-02 20:10 UTCEPSS rescore
  41. 2026-06-01 13:49 UTCEPSS rescore
  42. 2026-06-01 13:49 UTCEPSS rescore
  43. 2026-06-01 13:49 UTCEPSS rescore
  44. 2026-05-31 22:28 UTCEPSS rescore
  45. 2026-05-31 22:28 UTCEPSS rescore
  46. 2026-05-31 00:13 UTCEPSS rescore
  47. 2026-05-31 00:13 UTCEPSS rescore
  48. 2026-05-30 23:20 UTCEG score recompute
  49. 2026-05-29 13:40 UTCEPSS rescore
  50. 2026-05-28 13:42 UTCEPSS rescore
  51. 2026-05-28 13:42 UTCEPSS rescore
  52. 2026-05-28 13:42 UTCEPSS rescore
  53. 2026-05-27 13:38 UTCEPSS rescore
  54. 2026-05-27 13:37 UTCEPSS rescore
  55. 2026-05-27 13:37 UTCEPSS rescore
  56. 2026-05-26 13:41 UTCEPSS rescore
  57. 2026-05-26 13:41 UTCEPSS rescore
  58. 2026-05-26 07:16 UTCEPSS rescore
  59. 2026-05-26 07:16 UTCEPSS rescore
  60. 2026-05-25 22:16 UTCOSV refresh
  61. 2026-05-24 16:42 UTCEPSS rescore
  62. 2026-05-22 21:15 UTCEPSS rescore
  63. 2026-05-22 21:15 UTCEPSS rescore
  64. 2026-05-21 22:38 UTCEPSS rescore
  65. 2026-05-20 22:36 UTCEPSS rescore
  66. 2026-05-20 22:36 UTCEPSS rescore
  67. 2026-05-20 11:20 UTCEPSS rescore
  68. 2026-05-20 11:20 UTCEPSS rescore
  69. 2026-05-18 21:29 UTCEPSS rescore
  70. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2008-0299?
CVE-2008-0299 is a none vulnerability published on January 16, 2008. common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.
When was CVE-2008-0299 disclosed?
CVE-2008-0299 was first published in the National Vulnerability Database on January 16, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-0299 actively exploited?
CVE-2008-0299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2008-0299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-0299, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2008-0299?

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

Start Free Scan →Browse All CVEs