CVE-2026-47241

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: 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 string argument which is only validated to prevent CRLF injection and then sent verbatim. If this string is derived from user-controlled input, an attacker can force the next command to be absorbed as a continuation of the first command. This will cause the first command to eventually fail, but also prevents it from returning until another command is sent (from another thread). That other command will not return until the connection is closed. This vulnerability is fixed in 0.6.5 and 0.5.15.

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

Published

June 9, 2026

Last Modified

June 23, 2026

References (1)

Vendor Advisories for CVE-2026-47241(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatruby3-3-main-3.3.10-23.4.hum12026-07-15redhat
redhatruby3-4-main-3.4.8-31.3.hum12026-07-01redhat
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(3)

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 9× in last 7d / 41× 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-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 11:04 UTCEG score recompute
  3. 2026-08-23 11:04 UTCVendor advisory
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 15:42 UTCEG score recompute
  9. 2026-08-19 15:42 UTCVendor advisory
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 04:00 UTCEG score recompute
  15. 2026-08-15 04:00 UTCVendor advisory
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-12 01:22 UTCEG score recompute
  20. 2026-08-12 01:22 UTCVendor advisory
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-08 22:45 UTCEG score recompute
  24. 2026-08-08 22:45 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
Show 65 more
  1. 2026-08-06 13:47 UTCEPSS rescore
  2. 2026-08-05 20:07 UTCEG score recompute
  3. 2026-08-05 20:07 UTCVendor advisory
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:39 UTCEPSS rescore
  7. 2026-08-03 10:36 UTCEPSS rescore
  8. 2026-08-02 12:46 UTCEG score recompute
  9. 2026-08-02 12:46 UTCVendor advisory
  10. 2026-08-02 02:27 UTCEPSS rescore
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-07-30 16:28 UTCEPSS rescore
  13. 2026-07-30 10:08 UTCEG score recompute
  14. 2026-07-30 10:08 UTCVendor advisory
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-28 15:37 UTCEPSS rescore
  17. 2026-07-26 21:08 UTCEG score recompute
  18. 2026-07-26 21:08 UTCVendor advisory
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-24 14:18 UTCEPSS rescore
  22. 2026-07-23 14:18 UTCEPSS rescore
  23. 2026-07-23 03:17 UTCEG score recompute
  24. 2026-07-22 14:08 UTCEPSS rescore
  25. 2026-07-21 15:24 UTCEPSS rescore
  26. 2026-07-20 17:08 UTCEPSS rescore
  27. 2026-07-19 14:31 UTCEPSS rescore
  28. 2026-07-19 02:29 UTCEPSS rescore
  29. 2026-07-18 10:04 UTCEPSS rescore
  30. 2026-07-16 17:03 UTCEPSS rescore
  31. 2026-07-15 16:57 UTCEPSS rescore
  32. 2026-07-15 02:00 UTCEPSS rescore
  33. 2026-07-14 21:19 UTCVendor advisory
  34. 2026-07-13 22:30 UTCEPSS rescore
  35. 2026-07-13 06:13 UTCEPSS rescore
  36. 2026-07-12 05:46 UTCEPSS rescore
  37. 2026-07-11 18:17 UTCVendor advisory
  38. 2026-07-11 08:27 UTCEPSS rescore
  39. 2026-07-09 19:10 UTCEPSS rescore
  40. 2026-07-08 15:26 UTCVendor advisory
  41. 2026-07-08 15:16 UTCEPSS rescore
  42. 2026-07-07 13:46 UTCEPSS rescore
  43. 2026-07-06 16:27 UTCEPSS rescore
  44. 2026-07-06 02:23 UTCEPSS rescore
  45. 2026-07-05 12:10 UTCVendor advisory
  46. 2026-07-05 02:30 UTCEPSS rescore
  47. 2026-07-04 06:31 UTCEPSS rescore
  48. 2026-07-01 15:07 UTCEPSS rescore
  49. 2026-06-30 23:22 UTCEPSS rescore
  50. 2026-06-29 14:06 UTCEPSS rescore
  51. 2026-06-29 14:06 UTCEPSS rescore
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-27 03:08 UTCEPSS rescore
  56. 2026-06-25 13:49 UTCEPSS rescore
  57. 2026-06-24 14:05 UTCEPSS rescore
  58. 2026-06-23 21:33 UTCEPSS rescore
  59. 2026-06-23 21:33 UTCEPSS rescore
  60. 2026-06-22 21:40 UTCEG score recompute▲ 2.10
  61. 2026-06-22 21:37 UTCNVD updateCVSS v3 → 2.1 · CVSS v4 → 2.1
  62. 2026-06-14 23:18 UTCEPSS rescore
  63. 2026-06-13 23:00 UTCEPSS rescore
  64. 2026-06-12 23:12 UTCEPSS rescore
  65. 2026-06-09 19:18 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47241?
CVE-2026-47241 is a low 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 string argument which is only validated to prevent CRLF injection and then sent verbatim. If this string is derived from user-controlled…
When was CVE-2026-47241 disclosed?
CVE-2026-47241 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-47241 actively exploited?
CVE-2026-47241 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 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47241?
CVE-2026-47241 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-47241?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47241, 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-47241

Explore →

Is Your Infrastructure Affected by CVE-2026-47241?

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

Start Free Scan →Browse All CVEs