CVE-2018-6789

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 2021-11-03), 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, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 82%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

An issue was discovered in the base64d function in the SMTP listener in Exim before 4.90.1. By sending a handcrafted message, a buffer overflow may happen. This can be used to execute code remotely.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.6%
KEV
⚠ Exploited

Published

February 8, 2018

Last Modified

November 7, 2025

Advisory Details (9)

Auto-updated Jun 1, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 1274-1] exim4 security update

https://lists.debian.org/debian-lts-announce/2018/02/msg00009.html
generic

Exim Off-by-one RCE: Exploiting CVE-2018-6789 with Fully Mitigations Bypassing | DEVCORE

https://devco.re/blog/2018/03/06/exim-off-by-one-RCE-exploiting-CVE-2018-6789-en/
generic

oss-security - CVE-2018-6789 Exim 4.90 and earlier: buffer overflow

http://www.openwall.com/lists/oss-security/2018/02/07/2
generic

oss-security - Exim 4.90.1 released. (Was: CVE-2018-6789 Exim 4.90 and earlier: buffer overflow)

http://openwall.com/lists/oss-security/2018/02/10/2

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntueximon4 (4.86.2-2ubuntu2.3) @ xenial2026-07-18ubuntu

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.

Weakness Classification(2)

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

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 84× in last 7d / 340× 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 592 total refreshes for this CVE.

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

Publicly available exploits

(6 references)

Working exploit code is in the public domain (4 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCthistehneisen/CVE-2018-6789-Python3
    First seen Aug 5, 2023

    Exim < 4.90.1 RCE Vulnerability remake for Python3 with arguments passed from CLI

    Open source ↗
  • GitHub PoCmartinclauss/exim-rce-cve-2018-6789
    First seen Mar 2, 2020

    This repository provides a learning environment to understand how an Exim RCE exploit for CVE-2018-6789 works.

    Open source ↗
  • GitHub PoCsynacktiv/Exim-CVE-2018-6789
    First seen Oct 10, 2019

    PoC materials to exploit CVE-2018-6789

    Open source ↗
  • GitHub PoCberaphin/CVE-2018-6789
    First seen Nov 8, 2018
    Open source ↗
  • Exploit-DBEDB-45671
    First seen Oct 24, 2018

    exim 4.90 - Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-44571
    First seen May 2, 2018

    Exim < 4.90.1 - 'base64d' Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2018-6789?
CVE-2018-6789 is a critical vulnerability published on February 8, 2018. An issue was discovered in the base64d function in the SMTP listener in Exim before 4.90.1. By sending a handcrafted message, a buffer overflow may happen. This can be used to execute code remotely.
When was CVE-2018-6789 disclosed?
CVE-2018-6789 was first published in the National Vulnerability Database on February 8, 2018, with the most recent update on November 7, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-6789 actively exploited?
Yes. CISA added CVE-2018-6789 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Exim Exim. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2018-6789?
CVE-2018-6789 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2018-6789?
CVE-2018-6789 affects Exim Exim. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2018-6789?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6789, 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-2018-6789

Explore →

Is Your Infrastructure Affected by CVE-2018-6789?

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