CVE-2003-0466

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 78% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Weaponized

Also known asEUVD-2003-0460 (ENISA EUVD) · GHSA-7c4w-gm97-vgqq (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 78%
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 78%CVSS: 9.8Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

Off-by-one error in the fb_realpath() function, as derived from the realpath function in BSD, may allow attackers to execute arbitrary code, as demonstrated in wu-ftpd 2.5.0 through 2.6.2 via commands that cause pathnames of length MAXPATHLEN+1 to trigger a buffer overflow, including (1) STOR, (2) RETR, (3) APPE, (4) DELE, (5) MKD, (6) RMD, (7) STOU, or (8) RNTO.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation78% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
78%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
78% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2003

Last Modified

June 16, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
Patch available.
Web page

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/9446
Web page

'Off-by-one Buffer Overflow Vulnerability in BSD libc realpath(3)' - MARC

http://marc.info/?l=bugtraq&m=106002488209129&w=2
Web page

'wu-ftpd-2.6.2 off-by-one remote exploit.' - MARC

http://marc.info/?l=bugtraq&m=106001702232325&w=2
Web page

'FreeBSD Security Advisory FreeBSD-SA-03:08.realpath' - MARC

http://marc.info/?l=bugtraq&m=106001410028809&w=2
Web page

'wu-ftpd fb_realpath() off-by-one bug' - MARC

http://marc.info/?l=bugtraq&m=105967301604815&w=2
Web page

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/9423

Vendor Advisories for CVE-2003-0466(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2003-07-31redhat
redhatpatch2003-07-31redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:3.0(1)
PackageVulnerable rangeFix by version rangeDependents
wu-ftpd—
  • every version up to 2.6.2-3woody1: fixed in 2.6.2-3woody1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 81× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 217 rows 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. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 13:26 UTCEchelonGraph re-scored
  2. 2026-11-22 13:26 UTCVendor advisory
  3. 2026-11-22 13:26 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  4. 2026-11-21 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  5. 2026-11-21 15:49 UTCVendor advisory
  6. 2026-11-21 15:49 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  7. 2026-11-20 18:12 UTCEchelonGraph re-scored
  8. 2026-11-20 18:12 UTCVendor advisory
  9. 2026-11-20 18:12 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  10. 2026-11-20 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  11. 2026-11-19 20:31 UTCEchelonGraph re-scored
  12. 2026-11-19 20:31 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  13. 2026-11-18 22:53 UTCEchelonGraph re-scored
  14. 2026-11-18 22:53 UTCVendor advisory
  15. 2026-11-18 22:53 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  16. 2026-11-18 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  17. 2026-11-18 01:16 UTCEchelonGraph re-scored
  18. 2026-11-18 01:16 UTCVendor advisory
  19. 2026-11-18 01:16 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  20. 2026-11-17 03:36 UTCEchelonGraph re-scored
  21. 2026-11-17 03:36 UTCVendor advisory
  22. 2026-11-17 03:36 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  23. 2026-11-16 05:57 UTCEchelonGraph re-scored
  24. 2026-11-16 05:57 UTCVendor advisory
  25. 2026-11-16 05:57 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
Show 75 more
  1. 2026-11-15 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  2. 2026-11-15 07:31 UTCEchelonGraph re-scored
  3. 2026-11-15 07:31 UTCVendor advisory
  4. 2026-11-15 07:31 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  5. 2026-11-14 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  6. 2026-11-14 09:54 UTCEchelonGraph re-scored
  7. 2026-11-14 09:54 UTCVendor advisory
  8. 2026-11-14 09:53 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  9. 2026-11-13 12:15 UTCEchelonGraph re-scored
  10. 2026-11-13 12:15 UTCVendor advisory
  11. 2026-11-13 12:15 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  12. 2026-11-12 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  13. 2026-11-12 14:35 UTCVendor advisory
  14. 2026-11-12 14:35 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  15. 2026-11-11 16:57 UTCEchelonGraph re-scored
  16. 2026-11-11 16:57 UTCVendor advisory
  17. 2026-11-11 16:57 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  18. 2026-11-11 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  19. 2026-11-10 19:19 UTCEchelonGraph re-scored
  20. 2026-11-10 19:19 UTCVendor advisory
  21. 2026-11-10 19:19 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  22. 2026-11-09 21:34 UTCEchelonGraph re-scored
  23. 2026-11-09 21:34 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  24. 2026-11-08 23:56 UTCEchelonGraph re-scored
  25. 2026-11-08 23:56 UTCVendor advisory
  26. 2026-11-08 23:56 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  27. 2026-11-08 02:17 UTCEchelonGraph re-scored
  28. 2026-11-08 02:17 UTCVendor advisory
  29. 2026-11-08 02:16 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  30. 2026-11-07 04:35 UTCEchelonGraph re-scored
  31. 2026-11-07 04:35 UTCVendor advisory
  32. 2026-11-07 04:35 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  33. 2026-11-06 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  34. 2026-11-06 06:58 UTCEchelonGraph re-scored
  35. 2026-11-06 06:58 UTCVendor advisory
  36. 2026-11-06 06:58 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  37. 2026-11-05 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  38. 2026-11-05 09:21 UTCEchelonGraph re-scored
  39. 2026-11-05 09:21 UTCVendor advisory
  40. 2026-11-05 09:21 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  41. 2026-11-04 11:43 UTCEchelonGraph re-scored
  42. 2026-11-04 11:43 UTCVendor advisory
  43. 2026-11-04 11:43 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  44. 2026-11-03 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  45. 2026-11-03 14:05 UTCEchelonGraph re-scored
  46. 2026-11-03 14:05 UTCVendor advisory
  47. 2026-11-03 14:05 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  48. 2026-11-02 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  49. 2026-11-02 16:17 UTCVendor advisory
  50. 2026-11-02 16:17 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  51. 2026-11-01 18:31 UTCEchelonGraph re-scored
  52. 2026-11-01 18:31 UTCVendor advisory
  53. 2026-11-01 18:30 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  54. 2026-10-31 20:52 UTCEchelonGraph re-scored
  55. 2026-10-31 20:52 UTCVendor advisory
  56. 2026-10-31 20:52 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  57. 2026-10-31 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  58. 2026-10-30 23:15 UTCEchelonGraph re-scored
  59. 2026-10-30 23:15 UTCVendor advisory
  60. 2026-10-30 23:15 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  61. 2026-10-30 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  62. 2026-10-30 01:38 UTCEchelonGraph re-scored
  63. 2026-10-30 01:38 UTCVendor advisory
  64. 2026-10-30 01:38 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  65. 2026-10-29 04:01 UTCEchelonGraph re-scored
  66. 2026-10-29 04:01 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  67. 2026-10-28 16:25 UTCEPSS rescoreEPSS 78% · 99th percentile
  68. 2026-10-28 06:23 UTCEchelonGraph re-scored
  69. 2026-10-28 06:23 UTCVendor advisory
  70. 2026-10-28 06:23 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  71. 2026-10-27 16:24 UTCEPSS rescoreEPSS 78% · 99th percentile
  72. 2026-10-27 08:46 UTCEchelonGraph re-scored
  73. 2026-10-27 08:46 UTCVendor advisory
  74. 2026-10-27 08:46 UTCGHSA enrichmentGHSA-7c4w-gm97-vgqq · GitHub severity HIGH
  75. 2026-10-26 09:16 UTCVendor advisory

Publicly available exploits

(5 references)

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

  • Exploit-DBEDB-78✓ verified
    Published Aug 11, 2003

    WU-FTPD 2.6.2 - Remote Command Execution

    Open source ↗
  • Exploit-DBEDB-22975✓ verified
    Published Aug 6, 2003

    WU-FTPD 2.6.0/2.6.1/2.6.2 - 'realpath()' Off-by-One Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-74✓ verified
    Published Aug 3, 2003

    WU-FTPD 2.6.2 - Off-by-One Remote Command Execution

    Open source ↗
  • Exploit-DBEDB-22974✓ verified
    Published Aug 2, 2003

    WU-FTPD 2.6.2 - 'realpath()' Off-by-One Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-22976✓ verified
    Published Jul 31, 2003

    FreeBSD 4.8 - 'realpath()' Off-by-One Buffer Overflow

    Open source ↗

Frequently asked(5)

What is CVE-2003-0466?
CVE-2003-0466 is a critical-severity vulnerability; its CVE record was published on August 27, 2003. Off-by-one error in the fb_realpath() function, as derived from the realpath function in BSD, may allow attackers to execute arbitrary code, as demonstrated in wu-ftpd 2.5.0 through 2.6.2 via commands that cause pathnames of length MAXPATHLEN+1 to trigger a buffer overflow, including (1) STOR, (2)…
When was CVE-2003-0466 made public?
CVE-2003-0466 was made public on July 31, 2003: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2003. EchelonGraph's copy of the record carries a last-modified date of June 16, 2026; the record at its source may have been updated since.
Is CVE-2003-0466 actively exploited?
CVE-2003-0466 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2003-0466?
CVE-2003-0466 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2003-0466?
A fix for CVE-2003-0466 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2003-0466 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2003-0466

Explore →

Is Your Infrastructure Affected by CVE-2003-0466?

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