CVE-2026-42006

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-05-12. a secondary CVSS source baseline 4.3; sources differ by 0.0.

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

A fix is available — apply it.

An attacker can cause uncontrolled memory usage with excessive bracing over IMAP. The fix in CVE-2026-27857 was incomplete, only blocking one way of doing this, so there was still another way left open. In particular, the fix was for closing braces, but you could still use open braces to bypass the limit. Using excessive bracing, attacker can cause memory usage up to configured memory limit. Install fixed version, or configure vsz_limit for imap process to low value. No publicly available exploits are known.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity43% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

May 12, 2026

Last Modified

August 3, 2026

Advisory Details (1)

Auto-updated Jun 17, 2026
No patch confirmed yet.
generic
https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0002.json

Vendor Advisories for CVE-2026-42006(7)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudovecot-submissiond (1:2.4.2+dfsg1-3ubuntu2.1) @ resolute2026-08-23ubuntu
redhatdovecot-1:2.2.36-8.el7_9.22026-08-03redhat
redhatdovecot-1:2.3.16-3.el8_8.22026-07-27redhat
redhatdovecot-1:2.3.16-8.el8_102026-07-27redhat
redhatdovecot-1:2.3.16-2.el8_6.22026-07-27redhat
redhatdovecot-1:2.3.8-9.el8_4.22026-07-27redhat
redhatdovecot-1:2.3.16-15.el9_6.22026-07-23redhat
redhatdovecot-1:2.3.16-8.el9_2.32026-07-23redhat
redhatdovecot-1:2.3.16-11.el9_4.32026-07-23redhat
redhatdovecot-1:2.3.16-18.el9_8.12026-07-20redhat
redhatdovecot-1:2.3.21-16.el10_0.22026-07-20redhat
redhatdovecot-1:2.3.21-19.el10_2.12026-07-20redhat

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

(6 across 6 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
dovecot—2.4.4-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
dovecot—2.4.4-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.3.13+dfsg1-2, 1:2.3.13+dfsg1-2+deb11u1, 1:2.3.13+dfsg1-2+deb11u2, 1:2.3.13+dfsg1-2+deb11u31:2.3.13+dfsg1-2+deb11u4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.3.19.1+dfsg1-2.1 ... 1:2.3.19.1+dfsg1-2.1+deb12u5 (6 versions)1:2.3.19.1+dfsg1-2.1+deb12u6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.1+dfsg1-6+deb13u5 (6 versions)1:2.4.1+dfsg1-6+deb13u6—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
dovecot1:2.4.1+dfsg1-6 ... 1:2.4.3+dfsg1-2 (10 versions)1:2.4.4+dfsg1-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

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 7× in last 7d / 32× 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 243 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-42006?
CVE-2026-42006 is a medium vulnerability published on May 12, 2026. An attacker can cause uncontrolled memory usage with excessive bracing over IMAP. The fix in CVE-2026-27857 was incomplete, only blocking one way of doing this, so there was still another way left open. In particular, the fix was for closing braces, but you could still use open braces to bypass the…
When was CVE-2026-42006 disclosed?
CVE-2026-42006 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42006 actively exploited?
CVE-2026-42006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-42006?
CVE-2026-42006 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-42006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42006, 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-2026-42006

Explore →

Is Your Infrastructure Affected by CVE-2026-42006?

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

Start Free Scan →Browse All CVEs