CVE-2009-1617

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (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: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.5% 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
Weaponized
7.5EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), public exploit)
CISA-KEV: Not listedEPSS PROB: 2.5%CVSS v2: 7.5Exploit: Exploit-DB (verified) · public exploitExposed services: Not assessed

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

Teraway LinkTracker 1.0 allows remote attackers to bypass authentication and gain administrative access via a userid=1&lvl=1 value for the twLTadmin cookie.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
64
EG Risk 64/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
Severity75% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
2.5%
EPSS %ILE
84th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · 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 12, 2009

Last Modified

April 23, 2026

References (3)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 15× 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 79 of 112 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. 21 repeat rows among the latest 100 are merged into the row they repeat. The 33 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.5% · 84th percentile
  2. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  3. 2026-10-08 16:33 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  4. 2026-10-07 23:37 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  5. 2026-10-06 15:09 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  6. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  7. 2026-09-30 14:58 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  8. 2026-09-29 07:58 UTCEG score recompute
  9. 2026-09-27 13:39 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  10. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  11. 2026-09-24 13:57 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  12. 2026-09-17 19:20 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  13. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  14. 2026-09-13 16:40 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  15. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  16. 2026-09-10 09:24 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  17. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  18. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  19. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  20. 2026-08-28 21:34 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  21. 2026-08-27 14:19 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  22. 2026-08-25 13:43 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  23. 2026-08-19 16:58 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  24. 2026-08-15 01:24 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  25. 2026-08-09 13:41 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
Show 54 more
  1. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  2. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  3. 2026-08-03 10:28 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  4. 2026-07-30 16:22 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  5. 2026-07-30 01:26 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  6. 2026-07-26 13:38 UTCEG score recompute▲ 7.50
  7. 2026-07-25 14:12 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  8. 2026-07-24 14:12 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  9. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  10. 2026-07-23 00:59 UTCEG score recompute
  11. 2026-07-23 00:37 UTCEG score recompute
  12. 2026-07-23 00:03 UTCEG score recompute
  13. 2026-07-22 21:42 UTCEG score recompute
  14. 2026-07-22 14:03 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  15. 2026-07-21 15:20 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  16. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  17. 2026-07-18 09:59 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  18. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  19. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  20. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  21. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  22. 2026-07-13 06:07 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  23. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  24. 2026-07-09 19:04 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  25. 2026-07-08 15:10 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  26. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  27. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  28. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  29. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  30. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.5% · 83rd percentile
  31. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  32. 2026-06-29 14:02 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  33. 2026-06-28 14:03 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  34. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  35. 2026-06-27 03:05 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  36. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  37. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  38. 2026-06-23 21:29 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  39. 2026-06-22 14:22 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  40. 2026-06-21 14:53 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  41. 2026-06-21 01:56 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  42. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  43. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  44. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  45. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  46. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.5% · 82nd percentile
  47. 2026-06-14 23:14 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  48. 2026-06-13 22:57 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  49. 2026-06-12 23:08 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  50. 2026-06-10 22:14 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  51. 2026-06-10 13:17 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  52. 2026-06-08 14:13 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  53. 2026-06-07 15:22 UTCEPSS rescoreEPSS 1.9% · 83rd percentile
  54. 2026-06-06 13:44 UTCEPSS rescoreEPSS 1.9% · 83rd percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-8550✓ verified
    Published Apr 27, 2009

    Teraway LinkTracker 1.0 - Insecure Cookie Handling

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2009-1617?
CVE-2009-1617 is a high vulnerability published on May 12, 2009. Teraway LinkTracker 1.0 allows remote attackers to bypass authentication and gain administrative access via a userid=1&lvl=1 value for the twLTadmin cookie.
When was the CVE record for CVE-2009-1617 published?
The CVE record for CVE-2009-1617 was published on May 12, 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-1617 actively exploited?
CVE-2009-1617 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 2.5% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-1617?
No fix for CVE-2009-1617 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-1617

Explore →

Is Your Infrastructure Affected by CVE-2009-1617?

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

Book a Demo →Browse All CVEs