CVE-2026-42246

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 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.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 0

A fix is available — apply it.

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to versions 0.3.10, 0.4.24, 0.5.14, and 0.6.4, a man-in-the-middle attacker can cause Net::IMAP#starttls to return "successfully", without starting TLS. This issue has been patched in versions 0.3.10, 0.4.24, 0.5.14, and 0.6.4.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
—
EPSS
24.8%
KEV
Not listed

Published

May 9, 2026

Last Modified

July 15, 2026

Advisory Details (8)

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

STARTTLS stripping via invalid response timing · Advisory · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/security/advisories/GHSA-vcgp-9326-pqcp
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

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

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

🔀 Merge pull request #665 from ruby/backport/v0.5/STARTTLS-stripping · ruby/net-imap@f79d35b · GitHub

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

🔀 Merge pull request #667 from ruby/backport/v0.3/STARTTLS-stripping · ruby/net-imap@97e2488 · GitHub

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

🔀 Merge pull request #666 from ruby/backport/v0.4/STARTTLS-stripping · ruby/net-imap@24a4e77 · GitHub

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

🔀 Merge pull request #664 from ruby/security/STARTTLS-stripping · ruby/net-imap@0ede4c4 · GitHub

https://github.com/ruby/net-imap/commit/0ede4c40b1523dfeaf95777b2678e54cc0fd9618

Vendor Advisories for CVE-2026-42246(20)

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
ubunturuby2.3-tcltk (2.3.1-2~ubuntu16.04.16+esm14) @ xenial2026-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.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
net-imap0.1.0 ... 0.3.9 (19 versions)0.3.10—

Weakness Classification(6)

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 6× in last 7d / 34× 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.

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

Frequently asked(5)

What is CVE-2026-42246?
CVE-2026-42246 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.3.10, 0.4.24, 0.5.14, and 0.6.4, a man-in-the-middle attacker can cause Net::IMAP#starttls to return "successfully", without starting TLS. This issue has been patched in versions 0.3.10,…
When was CVE-2026-42246 disclosed?
CVE-2026-42246 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42246 actively exploited?
CVE-2026-42246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42246?
CVE-2026-42246 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-42246?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42246, 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-42246

Explore →

Is Your Infrastructure Affected by CVE-2026-42246?

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

Start Free Scan →Browse All CVEs