CVE-2010-4344

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 72%CVSS: 9.8Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

Heap-based buffer overflow in the string_vformat function in string.c in Exim before 4.70 allows remote attackers to execute arbitrary code via an SMTP session that includes two MAIL commands in conjunction with a large message containing crafted headers, leading to improper rejection logging.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
72%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

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

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

December 14, 2010

Last Modified

April 21, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
Patch available.
generic

Secunia Research & Vulnerability Insights | Flexera

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

oss-security - Exim remote root

http://openwall.com/lists/oss-security/2010/12/10/1
generic

Re: [exim-dev] Remote root vulnerability in Exim

http://lists.exim.org/lurker/message/20101210.164935.385e04d0.en.html
generic

Exim Internet Mailer

http://git.exim.org/exim.git/commit/24c929a27415c7cfc7126c47e4cad39acf3efa6b
generic

Exim Internet Mailer

http://bugs.exim.org/show_bug.cgi?id=787
generic

Secunia Research & Vulnerability Insights | Flexera

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

Secunia Research & Vulnerability Insights | Flexera

http://secunia.com/advisories/40019

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuexim4-daemon-light (4.69-2ubuntu0.2) @ hardy2026-10-11ubuntu
redhatexim-0:4.63-3.el5_4.12010-12-10redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
exim4—
  • every version up to 4.70-1: fixed in 4.70-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
exim4—
  • every version up to 4.70-1: fixed in 4.70-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
exim4—
  • every version up to 4.70-1: fixed in 4.70-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
exim4—
  • every version up to 4.70-1: fixed in 4.70-1
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
exim44.69-9
  • every version up to 4.69-9+lenny1: fixed in 4.69-9+lenny1
—

Weakness Classification(1)

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

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 102× in last 7d / 435× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 1,932 refreshes 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 1,832 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-16925✓ verified
    Published Dec 16, 2010

    Exim4 < 4.69 - string_format Function Heap Buffer Overflow (Metasploit)

    Open source ↗
  • Exploit-DBEDB-15725✓ verified
    Published Dec 11, 2010

    Exim 4.63 - Remote Command Execution

    Open source ↗
  • Metasploitexploit/unix/smtp/exim4_string_format✓ verified
    Published Dec 10, 2010

    Exim4 string_format Function Heap Buffer Overflow

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(6)

What is CVE-2010-4344?
CVE-2010-4344 is a critical-severity vulnerability; its CVE record was published on December 14, 2010. Heap-based buffer overflow in the string_vformat function in string.c in Exim before 4.70 allows remote attackers to execute arbitrary code via an SMTP session that includes two MAIL commands in conjunction with a large message containing crafted headers, leading to improper rejection logging.
When was the CVE record for CVE-2010-4344 published?
The CVE record for CVE-2010-4344 was published on December 14, 2010. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 21, 2026; the record at its source may have been updated since.
Is CVE-2010-4344 actively exploited?
Yes. CISA added CVE-2010-4344 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Exim Exim. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2010-4344?
CVE-2010-4344 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2010-4344?
CVE-2010-4344 affects Exim Exim. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2010-4344?
A fix for CVE-2010-4344 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2010-4344

Explore →

Is Your Infrastructure Affected by CVE-2010-4344?

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

Book a Demo →Browse All CVEs