CVE-2005-3120

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 23.3%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 23%CVSS: 9.8Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

Stack-based buffer overflow in the HTrjis function in Lynx 2.8.6 and earlier allows remote NNTP servers to execute arbitrary code via certain article headers containing Asian characters that cause Lynx to add extra escape (ESC) characters.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/100SSVC: Track*

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
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
23%
EPSS %ILE
98%
KEV
Not listed

Published

October 17, 2005

Last Modified

April 16, 2026

Advisory Details (6)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17248
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17238
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17231
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17230
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17216
generic

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/17150

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulynx () @ warty2026-05-20ubuntu
redhatlynx-0:2.8.5-18.12005-10-17redhat

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

(8 across 6 ecosystems)
Debian:3.0(2)
PackageVulnerable rangeFixed inDependents
lynx2.8.4.1b-3.22.8.4.1b-3.2—
lynx-cur2.8.5-2.52.8.5-2.5woody1—
Debian:3.1(2)
PackageVulnerable rangeFixed inDependents
lynx2.8.5-22.8.5-2sarge1—
lynx-cur2.8.6-92.8.6-9sarge1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
lynx—2.8.5-2sarge1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lynx—2.8.5-2sarge1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
lynx—2.8.5-2sarge1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
lynx—2.8.5-2sarge1—

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-1256✓ verified
    First seen Oct 17, 2005

    Lynx 2.8.6dev.13 - Remote Buffer Overflow (PoC)

    Open source ↗

Frequently asked(5)

What is CVE-2005-3120?
CVE-2005-3120 is a critical vulnerability published on October 17, 2005. Stack-based buffer overflow in the HTrjis function in Lynx 2.8.6 and earlier allows remote NNTP servers to execute arbitrary code via certain article headers containing Asian characters that cause Lynx to add extra escape (ESC) characters.
When was CVE-2005-3120 disclosed?
CVE-2005-3120 was first published in the National Vulnerability Database on October 17, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-3120 actively exploited?
CVE-2005-3120 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23% probability of exploitation in the next 30 days, which ranks it in the top 2.4% of all scored CVEs.
What is the CVSS score of CVE-2005-3120?
CVE-2005-3120 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2005-3120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-3120, 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-2005-3120

Explore →

Is Your Infrastructure Affected by CVE-2005-3120?

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

Start Free Scan →Browse All CVEs