CVE-2009-1629

MEDIUMCVSS v2 · 6.86.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.8 — 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:M/Au:N/C:P/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.3% 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_v2
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS v2: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ajaxterm.js in AjaxTerm 0.10 and earlier generates session IDs with predictable random numbers based on certain JavaScript functions, which makes it easier for remote attackers to (1) hijack a session or (2) cause a denial of service (session ID exhaustion) via a brute-force attack.

CVSS v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.8MEDIUMlow confidence
EG Risk
36
EG Risk 36/100CISA SSVC

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
Severity68% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
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.3%
EPSS %ILE
83rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 14, 2009

Last Modified

April 23, 2026

References (7)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
debian:10ajaxterm @ 0.10-5 (fixes >=0)—osv

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

(2 across 2 ecosystems)
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
ajaxterm0.9-2
  • every version up to 0.9-2+etch1: fixed in 0.9-2+etch1
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
ajaxterm0.10-2
  • every version up to 0.10-2+lenny1: fixed in 0.10-2+lenny1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 18× 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 83 of 122 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. 17 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-10 19:54 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  2. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  3. 2026-10-08 16:33 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  4. 2026-10-07 23:37 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-10-06 15:09 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  6. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  7. 2026-10-04 23:15 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  8. 2026-10-03 11:39 UTCOSV refresh
  9. 2026-09-30 14:58 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-09-29 07:58 UTCEG score recompute
  11. 2026-09-27 13:39 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  13. 2026-09-24 13:57 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-09-14 05:19 UTCOSV refresh
  17. 2026-09-13 16:40 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  18. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-09-10 09:24 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  22. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-08-28 21:34 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  24. 2026-08-27 14:19 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  25. 2026-08-26 06:13 UTCOSV refresh
Show 58 more
  1. 2026-08-25 13:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-08-19 16:58 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  3. 2026-08-15 01:24 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  4. 2026-08-09 22:40 UTCOSV refresh
  5. 2026-08-09 13:41 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  6. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  7. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  8. 2026-08-03 10:28 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  9. 2026-07-30 16:22 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  10. 2026-07-30 01:26 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  11. 2026-07-26 13:38 UTCEG score recompute▲ 6.80
  12. 2026-07-25 14:12 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  13. 2026-07-24 23:11 UTCOSV refresh
  14. 2026-07-24 14:12 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  15. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  16. 2026-07-23 00:59 UTCEG score recompute
  17. 2026-07-23 00:37 UTCEG score recompute
  18. 2026-07-23 00:03 UTCEG score recompute
  19. 2026-07-22 21:42 UTCEG score recompute
  20. 2026-07-22 14:03 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  21. 2026-07-21 15:20 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  22. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  23. 2026-07-18 09:59 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  24. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  25. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  26. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  27. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  28. 2026-07-13 06:07 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  29. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  30. 2026-07-09 19:04 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  31. 2026-07-08 15:10 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  32. 2026-07-07 18:12 UTCOSV refresh
  33. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  34. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  35. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  36. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  37. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  38. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  39. 2026-06-29 14:02 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  40. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  41. 2026-06-27 03:05 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  42. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  43. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  44. 2026-06-23 21:29 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  45. 2026-06-21 14:53 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  46. 2026-06-21 01:56 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  47. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  48. 2026-06-19 05:55 UTCOSV refresh
  49. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  50. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  51. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  52. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  53. 2026-06-14 23:14 UTCEPSS rescoreEPSS 1.0% · 77th percentile
  54. 2026-06-13 22:57 UTCEPSS rescoreEPSS 1.0% · 77th percentile
  55. 2026-06-12 23:08 UTCEPSS rescoreEPSS 1.0% · 77th percentile
  56. 2026-06-10 22:14 UTCEPSS rescoreEPSS 1.0% · 77th percentile
  57. 2026-06-10 13:17 UTCEPSS rescoreEPSS 1.0% · 77th percentile
  58. 2026-06-08 14:13 UTCEPSS rescoreEPSS 1.0% · 77th percentile

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2009-1629?
CVE-2009-1629 is a medium vulnerability published on May 14, 2009. ajaxterm.js in AjaxTerm 0.10 and earlier generates session IDs with predictable random numbers based on certain JavaScript functions, which makes it easier for remote attackers to (1) hijack a session or (2) cause a denial of service (session ID exhaustion) via a brute-force attack.
When was the CVE record for CVE-2009-1629 published?
The CVE record for CVE-2009-1629 was published on May 14, 2009. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-2009-1629 actively exploited?
CVE-2009-1629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-1629?
A fix for CVE-2009-1629 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-2009-1629

Explore →

Is Your Infrastructure Affected by CVE-2009-1629?

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

Book a Demo →Browse All CVEs