CVE-2004-0399

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 20.5% 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
Weaponized
7.5EG
EchelonGraph verdictMitigate 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: 21%CVSS v2: 7.5Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

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

Stack-based buffer overflow in Exim 3.35, and other versions before 4, when the sender_verify option is true, allows remote attackers to cause a denial of service and possibly execute arbitrary code during sender verification.

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
21%
EPSS %ILE
97th
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

July 7, 2004

Last Modified

June 16, 2026

References (12)

Affected Packages

(6 across 5 ecosystems)
Debian:3.0(2)
PackageVulnerable rangeFixed inDependents
exim—3.35-1woody3—
exim-tls3.35-3woody13.35-3woody2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
exim4—4.33-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
exim4—4.33-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
exim4—4.33-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
exim4—4.33-1—

Data Freshness Timeline

(refreshed 1× in last 7d / 4× 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-29 02:39 UTCEG score recompute
  2. 2026-09-16 03:24 UTCOSV refresh
  3. 2026-09-12 14:54 UTCEPSS rescore
  4. 2026-09-10 09:23 UTCEPSS rescore
  5. 2026-08-30 01:13 UTCEPSS rescore
  6. 2026-08-28 01:21 UTCOSV refresh
  7. 2026-08-11 15:03 UTCOSV refresh
  8. 2026-07-26 15:17 UTCOSV refresh
  9. 2026-07-26 13:24 UTCEG score recompute▲ 7.50
  10. 2026-07-25 14:11 UTCEPSS rescore
  11. 2026-07-24 14:11 UTCEPSS rescore
  12. 2026-07-23 00:45 UTCEG score recompute
  13. 2026-07-23 00:27 UTCEG score recompute
  14. 2026-07-22 23:50 UTCEG score recompute
  15. 2026-07-22 21:30 UTCEG score recompute
  16. 2026-07-20 17:02 UTCEPSS rescore
  17. 2026-07-18 09:59 UTCEPSS rescore
  18. 2026-07-18 09:59 UTCEPSS rescore
  19. 2026-07-16 16:58 UTCEPSS rescore
  20. 2026-07-13 06:07 UTCEPSS rescore
  21. 2026-07-11 08:22 UTCEPSS rescore
  22. 2026-07-11 08:22 UTCEPSS rescore
  23. 2026-07-09 09:16 UTCOSV refresh
  24. 2026-07-08 15:09 UTCEPSS rescore
  25. 2026-07-06 02:19 UTCEPSS rescore
Show 52 more
  1. 2026-07-04 06:26 UTCEPSS rescore
  2. 2026-07-02 14:00 UTCEPSS rescore
  3. 2026-06-28 14:02 UTCEPSS rescore
  4. 2026-06-28 04:52 UTCEPSS rescore
  5. 2026-06-27 03:04 UTCEPSS rescore
  6. 2026-06-23 21:29 UTCEPSS rescore
  7. 2026-06-22 14:22 UTCEPSS rescore
  8. 2026-06-21 01:56 UTCEPSS rescore
  9. 2026-06-20 22:12 UTCOSV refresh
  10. 2026-06-19 19:22 UTCEPSS rescore
  11. 2026-06-19 19:22 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-16 17:49 UTCEPSS rescore
  18. 2026-06-15 17:43 UTCEPSS rescore
  19. 2026-06-13 22:56 UTCEPSS rescore
  20. 2026-06-12 23:08 UTCEPSS rescore
  21. 2026-06-11 13:55 UTCEPSS rescore
  22. 2026-06-10 22:13 UTCEPSS rescore
  23. 2026-06-10 13:17 UTCEPSS rescore
  24. 2026-06-08 14:13 UTCEPSS rescore
  25. 2026-06-06 13:44 UTCEPSS rescore
  26. 2026-06-06 13:44 UTCEPSS rescore
  27. 2026-06-06 13:44 UTCEPSS rescore
  28. 2026-06-05 22:43 UTCEPSS rescore
  29. 2026-06-05 22:43 UTCEPSS rescore
  30. 2026-06-05 06:07 UTCEPSS rescore
  31. 2026-06-04 13:09 UTCEPSS rescore
  32. 2026-06-02 20:10 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-31 16:13 UTCEG score recompute
  35. 2026-05-31 16:13 UTCGHSA enrichment
  36. 2026-05-31 00:13 UTCEPSS rescore
  37. 2026-05-31 00:13 UTCEPSS rescore
  38. 2026-05-29 13:40 UTCEPSS rescore
  39. 2026-05-29 13:40 UTCEPSS rescore
  40. 2026-05-28 18:36 UTCOSV refresh
  41. 2026-05-28 13:42 UTCEPSS rescore
  42. 2026-05-28 13:42 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-26 07:16 UTCEPSS rescore
  46. 2026-05-24 16:42 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-20 22:36 UTCEPSS rescore
  49. 2026-05-20 11:20 UTCEPSS rescore
  50. 2026-05-20 11:20 UTCEPSS rescore
  51. 2026-05-18 21:29 UTCEPSS rescore
  52. 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-24093✓ verified
    First seen May 6, 2004

    Exim Sender 3.35 - Verification Remote Stack Buffer Overrun

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2004-0399?
CVE-2004-0399 is a high vulnerability published on July 7, 2004. Stack-based buffer overflow in Exim 3.35, and other versions before 4, when the sender_verify option is true, allows remote attackers to cause a denial of service and possibly execute arbitrary code during sender verification.
When was CVE-2004-0399 disclosed?
CVE-2004-0399 was first published on July 7, 2004, 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-2004-0399 actively exploited?
CVE-2004-0399 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 21% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-0399?
No fix for CVE-2004-0399 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-0399

Explore →

Is Your Infrastructure Affected by CVE-2004-0399?

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

Book a Demo →Browse All CVEs