CVE-2018-14362

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2018-6283 (ENISA EUVD) · GHSA-8wxh-p6hf-c3ph (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c does not forbid characters that may have unsafe interaction with message-cache pathnames, as demonstrated by a '/' character.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
46
EG Risk 46/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.
Exploitation3.7% × 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or 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.
EPSS PROB
3.7%
EPSS %ILE
89th
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.GitHub Security Advisory CVSS
EG Likelihood
3.7% 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 or medium mission impact; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or 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

July 17, 2018

Last Modified

November 21, 2024

Advisory Details (8)

Auto-updated Oct 6, 2026
Patch available. Sources: github_commit, redhat.
Web page

[SECURITY] [DSA 4277-1] mutt security update

https://www.debian.org/security/2018/dsa-4277
Web page

Mutt, NeoMutt: Multiple vulnerabilities (GLSA 201810-07) — Gentoo security

https://security.gentoo.org/glsa/201810-07
Web page

Release 2018-07-16 - NeoMutt

https://neomutt.org/2018/07/16/release
Web pageMentions a patch (unverified)

[SECURITY] [DLA 1455-1] mutt security update

https://lists.debian.org/debian-lts-announce/2018/08/msg00001.html
Web page

Sanitize POP bcache paths. (6aed28b4) · Commits · Mutt Project / mutt · GitLab

https://gitlab.com/muttmua/mutt/commit/6aed28b40a0410ec47d40c8c7296d8d10bae7576
GitHub commit Patch Available

commit 9bfab3552230 (neomutt/neomutt)

Patch available: neomutt/neomutt 20211029 (contains commit 9bfab3552230)

https://github.com/neomutt/neomutt/commit/9bfab35522301794483f8f9ed60820bdec9be59e
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:2526

Vendor Advisories for CVE-2018-14362(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumutt (1.5.21-5ubuntu2.3) @ precise2026-11-21ubuntu
ubuntumutt-patched (1.5.24-1ubuntu0.1) @ xenial2026-11-21ubuntu
ubuntumutt-patched (1.5.24-1ubuntu0.2) @ xenial2026-11-21ubuntu
ubuntuneomutt (20231103+dfsg1-1ubuntu0.1~esm1) @ noble2026-11-21ubuntu
redhatmutt-5:1.5.21-28.el7_52018-08-20redhat

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

Affected Packages

(14 across 10 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-1: fixed in 1.10.1-1
—
neomutt—
  • every version up to 20180716+dfsg.1-1: fixed in 20180716+dfsg.1-1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-1: fixed in 1.10.1-1
—
neomutt—
  • every version up to 20180716+dfsg.1-1: fixed in 20180716+dfsg.1-1
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-1: fixed in 1.10.1-1
—
neomutt—
  • every version up to 20180716+dfsg.1-1: fixed in 20180716+dfsg.1-1
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-1: fixed in 1.10.1-1
—
neomutt—
  • every version up to 20180716+dfsg.1-1: fixed in 20180716+dfsg.1-1
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-r0: fixed in 1.10.1-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-r0: fixed in 1.10.1-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-r0: fixed in 1.10.1-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
mutt—
  • every version up to 1.10.1-r0: fixed in 1.10.1-r0
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
mutt1.5.23-3
  • every version up to 1.5.23-3+deb8u1: fixed in 1.5.23-3+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
mutt1.7.2-1
  • every version up to 1.7.2-1+deb9u1: fixed in 1.7.2-1+deb9u1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 18× 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 322 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 222 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2018-14362?
CVE-2018-14362 is a critical-severity vulnerability; its CVE record was published on July 17, 2018. An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. pop.c does not forbid characters that may have unsafe interaction with message-cache pathnames, as demonstrated by a '/' character.
When was CVE-2018-14362 made public?
CVE-2018-14362 was made public on July 17, 2018: 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 July 17, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2018-14362 actively exploited?
CVE-2018-14362 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% probability of exploitation in the next 30 days (89th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-14362?
CVE-2018-14362 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-14362?
A fix for CVE-2018-14362 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-14362 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-2018-14362

Explore →

Is Your Infrastructure Affected by CVE-2018-14362?

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