CVE-2026-42246: net-imap vulnerable to STARTTLS stripping via invalid response timing
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.
Security readout for executives and security teams
Plain-English summary
Ruby applications using vulnerable net-imap versions can be fooled into thinking STARTTLS succeeded when it did not. A network-positioned attacker could then observe or alter IMAP traffic that operators expected to be encrypted. This matters most for systems handling mailbox credentials or sensitive email over untrusted networks.
Executive priority
Treat this as a high-priority dependency update for Ruby services that access email. The main business risk is silent loss of expected mail-channel encryption, exposing credentials or sensitive email contents to network attackers.
Technical view
CVE-2026-42246 affects Ruby net-imap before 0.3.10, 0.4.24, 0.5.14, and 0.6.4. A man-in-the-middle can abuse invalid response timing so Net::IMAP#starttls returns successfully without establishing TLS. The CVSS v4.0 score is 7.6, with high confidentiality and integrity impact.
Likely exposure
Exposure is limited to Ruby applications or packaged platforms using affected net-imap versions and STARTTLS for IMAP connections. Systems using patched gem versions or unaffected downstream packages are not indicated as exposed by the provided sources.
Exploitation context
The bundle does not indicate KEV listing or confirmed active exploitation. Exploitation requires a man-in-the-middle position and a victim application path that initiates STARTTLS using vulnerable Net::IMAP behavior.
Researcher notes
The key behavior is a false-success STARTTLS state in Net::IMAP#starttls. The sources provide affected version ranges, patched releases, commits, and Red Hat downstream advisories, but no proof-of-concept, active exploitation claim, or broader affected product list.
Mitigation direction
Upgrade net-imap to 0.3.10, 0.4.24, 0.5.14, 0.6.4, or later matching your branch.
Apply relevant Red Hat security advisories for packaged Ruby or net-imap components.
Inventory applications and images that include Ruby net-imap dependencies.
Check vendor guidance where net-imap is bundled by a distribution or product.
Validation and detection
Review Gemfile.lock, gemspecs, SBOMs, and container images for affected net-imap versions.
Identify code paths that call Net::IMAP#starttls for mailbox connections.
Confirm production and staging dependency resolution now selects a patched net-imap release.
For Red Hat systems, compare installed packages against the listed RHSA advisories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-325: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
32Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.