CVE-2001-0825

HIGHCVSS v2 · 10.010.0▲
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — 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:C/I:C/A:C. 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.6% 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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS v2: 10.0Exploit: NoneExposed: 0

A fix is available — apply it.

Buffer overflow in internal string handling routines of xinetd before 2.1.8.8 allows remote attackers to execute arbitrary commands via a length argument of zero or less, which disables the length check.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
51(Track)
EG Risk 51/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
Severity100% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
88%
KEV
Not listed

Published

December 6, 2001

Last Modified

June 16, 2026

References (10)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2001-07-06redhat

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.

All Vendor Advisories

(1)

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 6× in last 7d / 17× 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-26 13:21 UTCEG score recompute▲ 10.00
  2. 2026-07-23 00:43 UTCEG score recompute
  3. 2026-07-23 00:25 UTCEG score recompute
  4. 2026-07-22 23:48 UTCEG score recompute
  5. 2026-07-22 21:28 UTCEG score recompute
  6. 2026-07-20 17:02 UTCEPSS rescore
  7. 2026-07-18 09:59 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:53 UTCEPSS rescore
  10. 2026-07-15 01:55 UTCEPSS rescore
  11. 2026-07-11 08:22 UTCEPSS rescore
  12. 2026-07-08 15:08 UTCEPSS rescore
  13. 2026-07-04 06:26 UTCEPSS rescore
  14. 2026-07-02 14:00 UTCEPSS rescore
  15. 2026-06-29 14:02 UTCEPSS rescore
  16. 2026-06-28 14:02 UTCEPSS rescore
  17. 2026-06-27 03:04 UTCEPSS rescore
  18. 2026-06-24 14:01 UTCEPSS rescore
  19. 2026-06-23 21:29 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 01:56 UTCEPSS rescore
  22. 2026-06-19 19:22 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 40 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-14 23:13 UTCEPSS rescore
  3. 2026-06-13 22:56 UTCEPSS rescore
  4. 2026-06-12 23:07 UTCEPSS rescore
  5. 2026-06-11 13:55 UTCEPSS rescore
  6. 2026-06-10 22:13 UTCEPSS rescore
  7. 2026-06-10 13:17 UTCEPSS rescore
  8. 2026-06-08 14:13 UTCEPSS rescore
  9. 2026-06-07 15:21 UTCEPSS rescore
  10. 2026-06-06 13:44 UTCEPSS rescore
  11. 2026-06-05 06:07 UTCEPSS rescore
  12. 2026-06-04 13:09 UTCEPSS rescore
  13. 2026-06-02 20:10 UTCEPSS rescore
  14. 2026-06-01 13:48 UTCEPSS rescore
  15. 2026-05-31 22:27 UTCEPSS rescore
  16. 2026-05-31 19:54 UTCEG score recompute
  17. 2026-05-31 19:54 UTCVendor advisory
  18. 2026-05-31 19:54 UTCGHSA enrichment
  19. 2026-05-31 00:13 UTCEPSS rescore
  20. 2026-05-31 00:13 UTCEPSS rescore
  21. 2026-05-29 13:40 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-27 13:37 UTCEPSS rescore
  27. 2026-05-27 13:37 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-26 13:41 UTCEPSS rescore
  30. 2026-05-26 13:41 UTCEPSS rescore
  31. 2026-05-26 07:16 UTCEPSS rescore
  32. 2026-05-26 07:16 UTCEPSS rescore
  33. 2026-05-24 16:42 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-21 22:38 UTCEPSS rescore
  36. 2026-05-20 22:36 UTCEPSS rescore
  37. 2026-05-20 11:20 UTCEPSS rescore
  38. 2026-05-20 11:20 UTCEPSS rescore
  39. 2026-05-18 21:29 UTCEPSS rescore
  40. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2001-0825?
CVE-2001-0825 is a high vulnerability published on December 6, 2001. Buffer overflow in internal string handling routines of xinetd before 2.1.8.8 allows remote attackers to execute arbitrary commands via a length argument of zero or less, which disables the length check.
When was CVE-2001-0825 disclosed?
CVE-2001-0825 was first published in the National Vulnerability Database on December 6, 2001, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2001-0825 actively exploited?
CVE-2001-0825 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 11.7% of all scored CVEs.
How do I remediate CVE-2001-0825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2001-0825, 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

Explore the affected products and dependency analysis for CVE-2001-0825

Explore →

Is Your Infrastructure Affected by CVE-2001-0825?

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

Start Free Scan →Browse All CVEs