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.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 82%CVSS: 9.8Exploit: cisa kev · ssvc active · kev ransomware · epss top5pct · epss high · public exploitExposed: 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)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

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
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS PROB
82%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

February 8, 2018

Last Modified

November 7, 2025

Advisory Details (9)

Auto-updated Sep 3, 2026
⚠️ Active exploitation confirmed. 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 Internet Mailer

https://git.exim.org/exim.git/commit/cf3cd306062a08969c41a1cdd32c6855f1abecf1
generic
https://exim.org/static/doc/security/CVE-2018-6789.txt
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
http://www.securitytracker.com/id/1040461
generic🔴 Active Exploitation

CVE-2018-6789 - PSIRT.COM

http://www.securityfocus.com/bid/103049
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

Locked Out | Packet Storm

http://packetstormsecurity.com/files/162959/Exim-base64d-Buffer-Overflow.html
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-09-08ubuntu

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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
exim4—4.90.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
exim4—4.90.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
exim4—4.90.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
exim4—4.90.1-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
exim44.80-7 ... 4.80-7+deb7u5 (6 versions)4.80-7+deb7u6—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
exim44.84-8 ... 4.84.2-2+deb8u4 (10 versions)4.84.2-2+deb8u5—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
exim44.89-2, 4.89-2+deb9u1, 4.89-2+deb9u1~bpo8+1, 4.89-2+deb9u2, 4.89-2+deb9u3~bpo8+14.89-2+deb9u3—

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 76× in last 7d / 380× 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 1,199 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs