CVE-2026-42007

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-28. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
9.1EG
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: 0.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An attacker that has valid credentials can use a Sieve script with the editheader extension to trigger a use-after-free in the mail editing code, and to write memory contents beyond the intended buffer into the delivered mail. This causes memory leak and opportunity to do memory corruption during mail delivery, which can crash the delivery process and may allow execution of arbitrary code in the context of that process. Disable the Sieve editheader extension. Update to non-vulnerable version. No publicly available exploits are known.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

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

August 28, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
Patch available.
Web page
https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0003.json

Vendor Advisories for CVE-2026-42007(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatdovecot-1:2.3.16-18.el9_8.82026-10-12redhat
redhatdovecot-1:2.3.21-19.el10_2.82026-10-08redhat
redhatdovecot-1:2.3.16-16.el8_102026-10-06redhat

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)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.4.5-r0: fixed in 2.4.5-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot—
  • every version up to 2.4.5-r0: fixed in 2.4.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot1:2.3.19.1+dfsg1-2.1 ... 1:2.4.5+dfsg1-3 (43 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.1+dfsg1-6+deb13u6 (7 versions)
  • every version up to 1:2.4.1+dfsg1-6+deb13u7: fixed in 1:2.4.1+dfsg1-6+deb13u7
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.4+dfsg1-2 (12 versions)
  • every version up to 1:2.4.5+dfsg1-1: fixed in 1:2.4.5+dfsg1-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 208× 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 346 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 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42007?
CVE-2026-42007 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. An attacker that has valid credentials can use a Sieve script with the editheader extension to trigger a use-after-free in the mail editing code, and to write memory contents beyond the intended buffer into the delivered mail. This causes memory leak and opportunity to do memory corruption during…
When was the CVE record for CVE-2026-42007 published?
The CVE record for CVE-2026-42007 was published on August 28, 2026. 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 September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-42007 actively exploited?
CVE-2026-42007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42007?
CVE-2026-42007 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42007?
A fix for CVE-2026-42007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42007 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-2026-42007

Explore →

Is Your Infrastructure Affected by CVE-2026-42007?

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

Book a Demo →Browse All CVEs