Quick answers
- Is CVE-2026-42258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42258 being exploited in the wild.
- How severe is CVE-2026-42258?
- Critical severity, with a CVSS score of 9.8, published 9 May 2026.
- Which products and versions are affected?
- net-imap (RubyGems) ECOSYSTEM:introduced=0.6.0,fixed=0.6.4.
- Is there a fix for CVE-2026-42258?
- Yes. net-imap (RubyGems): upgrade to 0.6.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42258 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-42258?
- Check whether you run net-imap (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- net-imap (RubyGems): upgrade to 0.6.4 or later
bundle update net-imap
Technical details
The net-imap library fails to validate Symbol arguments, which are used to represent IMAP 'system flags'. Because these symbols are sent directly to the socket with a '\' prefix and no quoting or validation, an attacker can provide a Symbol containing CRLF sequences or spaces. This enables CRLF injection, allowing the attacker to terminate the intended IMAP command and inject arbitrary new commands (e.g., DELETE). The vulnerability is exploitable if the calling application converts untrusted user input into Symbols (via #to_sym or unsafe deserialization) before passing them to net-imap methods. Patches are available in versions 0.6.4, 0.5.14, and 0.4.24.
Affected products
- Ruby net-imap >= 0.6.0, <= 0.6.3
- Ruby net-imap >= 0.5.0, <= 0.5.13
- Ruby net-imap <= 0.4.23
Identifiers
- CVE-2026-42258
- GHSA-75xq-5h9v-w6px
Timeline
- 2026-04-24: disclosed: Initial disclosure in ruby/net-imap
- 2026-04-24: patched: Fixes released in versions 0.4.24, 0.5.14, and 0.6.4
- 2026-05-04: advisory: GitHub Advisory published
- 2026-05-09: other: NVD publication date