CVE-2026-47240

MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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, secondary
Trending — 3 sources updated this week
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0

A fix is available — apply it.

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a "raw data" argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals. A server without support for non-synchronizing literals may interpret the "+}\r\n" as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15.

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

Published

June 9, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Command Injection via non-synchronizing literal in "raw" argument · Advisory · ruby/net-imap · GitHub

https://github.com/ruby/net-imap/security/advisories/GHSA-8p34-64r3-mwg8

Vendor Advisories for CVE-2026-47240(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 / EcosystemFixed in / PatchReleasedSource
redhatruby3-3-main-3.3.10-23.4.hum12026-07-15redhat
redhatruby4-0-main-4.0.0-33.4.hum12026-06-30redhat
redhatruby3-3-main-3.3.10-23.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.5.9 (62 versions)0.5.15—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 15× in last 7d / 73× 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 122 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47240?
CVE-2026-47240 is a medium vulnerability published on June 9, 2026. Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a "raw data" argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing…
When was CVE-2026-47240 disclosed?
CVE-2026-47240 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47240 actively exploited?
CVE-2026-47240 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 60.0% of all scored CVEs.
What is the CVSS score of CVE-2026-47240?
CVE-2026-47240 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-47240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47240, 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-47240

Explore →

Is Your Infrastructure Affected by CVE-2026-47240?

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

Start Free Scan →Browse All CVEs