CVE-2024-49393

HIGHNVD 5.97.4▲
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2024-11-12. NVD baseline CVSS 5.9; sources differ by 1.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

In neomutt and mutt, the To and Cc email headers are not validated by cryptographic signing which allows an attacker that intercepts a message to change their value and include himself as a one of the recipients to compromise message confidentiality.

CVSS v3
5.9
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

November 12, 2024

Last Modified

June 26, 2026

Advisory Details (5)

Auto-updated Jun 26, 2026
Patch available. Sources: redhat, github_pr.
github_pr Patch Available

Protect more header fields

Patch available: neomutt/neomutt 20241002 (PR #4227 merged 2024-05-08)

https://github.com/neomutt/neomutt/pull/4227
github_pr Patch Available

ncrypt/crypt_gpgme.c: Show encryption information

Patch available: neomutt/neomutt 20241002 (PR #4221 merged 2024-05-08)

https://github.com/neomutt/neomutt/pull/4221
generic

Should To and Cc header fields be protected? · Issue #4223 · neomutt/neomutt · GitHub

https://github.com/neomutt/neomutt/issues/4223
redhat

2325317 – (CVE-2024-49393) CVE-2024-49393 mutt: neomutt: To and Cc email header fields are not protected by cryptographic signing

https://bugzilla.redhat.com/show_bug.cgi?id=2325317
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2024-49393

Vendor Advisories for CVE-2024-49393(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuneomutt (20231103+dfsg1-1ubuntu0.1~esm1) @ noble2026-05-23ubuntu

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

(8 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
mutt2.0.5-4.1 ... 2.4.1-1 (18 versions)——
neomutt20201127+dfsg.1-1.2 ... 20260616+dfsg-1 (34 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
mutt2.2.12-0.1 ... 2.4.1-1 (8 versions)——
neomutt20220429+dfsg1-4.1 ... 20260616+dfsg-1 (28 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
mutt2.2.13-1, 2.2.13-1+deb13u1, 2.3.2-1, 2.4.0-1, 2.4.1-1——
neomutt—20241002+dfsg-1—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
mutt2.2.13-1, 2.3.2-1, 2.4.0-1, 2.4.1-1——
neomutt—20241002+dfsg-1—

Weakness Classification(1)

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 8× in last 7d / 33× 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 169 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-49393?
CVE-2024-49393 is a high vulnerability published on November 12, 2024. In neomutt and mutt, the To and Cc email headers are not validated by cryptographic signing which allows an attacker that intercepts a message to change their value and include himself as a one of the recipients to compromise message confidentiality.
When was CVE-2024-49393 disclosed?
CVE-2024-49393 was first published in the National Vulnerability Database on November 12, 2024, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-49393 actively exploited?
CVE-2024-49393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2024-49393?
CVE-2024-49393 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
How do I remediate CVE-2024-49393?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-49393, 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-2024-49393

Explore →

Is Your Infrastructure Affected by CVE-2024-49393?

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

Start Free Scan →Browse All CVEs