CVE-2026-42245

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.4.24, 0.5.14, and 0.6.4, Net::IMAP::ResponseReader has quadratic time complexity when reading large responses containing many string literals. A hostile server can send responses which are crafted to exhaust the client's CPU for a denial of service attack. This issue has been patched in versions 0.4.24, 0.5.14, and 0.6.4.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

May 9, 2026

Last Modified

July 24, 2026

Advisory Details (7)

Auto-updated May 18, 2026
Patch available. Sources: github.
github Patch Available

Quadratic complexity when reading response literals · Advisory · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/security/advisories/GHSA-q2mw-fvj9-vvcw
generic

Release v0.6.4 · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/releases/tag/v0.6.4
generic

Release v0.5.14 · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/releases/tag/v0.5.14
generic

Release v0.4.24 · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/releases/tag/v0.4.24
generic

🔀 Merge pull request #642 from ruby/response_reader-performance · ruby/net-imap@de685f9 · GitHub

https://github.com/ruby/net-imap/commit/de685f91a4a4cc75eb80da898c2bf8af08d34819
generic

🔀 Merge pull request #651 from ruby/backport/v0.4/response_reader-non… · ruby/net-imap@88d9523 · GitHub

https://github.com/ruby/net-imap/commit/88d95231fc8afef11c1f074453f7d75b68c9dfda
generic

🔀 Merge pull request #650 from ruby/backport/v0.5/response_reader-non… · ruby/net-imap@6091f7d · GitHub

https://github.com/ruby/net-imap/commit/6091f7d6b1f3514cafbfe39c76f2b5d73de3ca96

Vendor Advisories for CVE-2026-42245(12)

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
redhatruby3-4-main-3.4.10-31.hum12026-07-13redhat
redhatruby:3.3-9060020260630075016.92026-07-09redhat
redhatruby:3.3-9040020260630065449.92026-07-07redhat
redhatruby-0:3.3.10-11.el10_0.22026-07-06redhat
redhatruby4-0-main-4.0.0-33.4.hum12026-06-30redhat
redhatruby4.0-0:4.0.3-35.el10_22026-06-30redhat
redhatruby:4.0-9080020260619130154.92026-06-30redhat
redhatruby-0:3.3.10-13.el10_22026-06-30redhat
redhatruby3-3-main-3.3.10-23.2.hum12026-06-30redhat
redhatruby:3.3-8100020260615131010.489197e62026-06-30redhat
redhatruby:3.3-9080020260615131001.92026-06-30redhat
redhatruby3-4-main-3.4.8-31.2.hum12026-06-30redhat

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)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby2.72.7.4-1 ... 2.7.5-1 (8 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby3.13.1.2-7 ... 3.1.2-8.5 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby3.33.3.8-2, 3.3.8-2.1, 3.3.8-2.2——
RubyGems(1)
PackageVulnerable rangeFixed inDependents
net-imap0.1.0 ... 0.4.9.1 (45 versions)0.4.24—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 27× 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 179 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42245?
CVE-2026-42245 is a high vulnerability published on May 9, 2026. Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.4.24, 0.5.14, and 0.6.4, Net::IMAP::ResponseReader has quadratic time complexity when reading large responses containing many string literals. A hostile server can send responses which are…
When was CVE-2026-42245 disclosed?
CVE-2026-42245 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42245 actively exploited?
CVE-2026-42245 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 65.0% of all scored CVEs.
What is the CVSS score of CVE-2026-42245?
CVE-2026-42245 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42245, 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-42245

Explore →

Is Your Infrastructure Affected by CVE-2026-42245?

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

Start Free Scan →Browse All CVEs