CVE-2010-1512

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — 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:N/I:P/A:N. 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 3.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS v2: 4.3Exploit: None knownExposed: 0

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

Directory traversal vulnerability in aria2 before 1.9.3 allows remote attackers to create arbitrary files via directory traversal sequences in the name attribute of a file element in a metalink file.

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(low)
EG Risk
25(Track)
EG Risk 25/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
Severity43% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
87%
KEV
Not listed

Published

May 17, 2010

Last Modified

April 29, 2026

References (38)

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
aria2—1.9.3-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
aria2—1.9.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
aria20.10.1-1 ... 1.9.1-1 (30 versions)1.9.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
aria20.10.1-1 ... 1.9.1-1 (30 versions)1.9.3-1—
Debian:5.0(1)
PackageVulnerable rangeFixed inDependents
aria20.14.0-1, 0.14.0-1+lenny10.14.0-1+lenny2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 12× 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.

Showing the most recent 100 of 128 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2010-1512?
CVE-2010-1512 is a medium vulnerability published on May 17, 2010. Directory traversal vulnerability in aria2 before 1.9.3 allows remote attackers to create arbitrary files via directory traversal sequences in the name attribute of a file element in a metalink file.
When was CVE-2010-1512 disclosed?
CVE-2010-1512 was first published in the National Vulnerability Database on May 17, 2010, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-1512 actively exploited?
CVE-2010-1512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 12.6% of all scored CVEs.
How do I remediate CVE-2010-1512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-1512, 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-2010-1512

Explore →

Is Your Infrastructure Affected by CVE-2010-1512?

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

Book a Demo →Browse All CVEs