CVE-2026-42006

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 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)
EPSS
39.7%
KEV
Not listed

Published

May 12, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jun 17, 2026
No patch confirmed yet.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudovecot-submissiond (1:2.4.2+dfsg1-3ubuntu2.1) @ resolute2026-06-28ubuntu

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.

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

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

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 July 21, 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 39.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.