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 affected net-imap versions may believe an email connection is encrypted when TLS never started. An attacker positioned between the application and IMAP server could exploit response timing to expose or alter email traffic and credentials. Patched releases are available.
Executive priority
Treat as a high-priority upgrade for systems processing sensitive email through STARTTLS. Accelerate remediation where IMAP traffic crosses untrusted or externally controlled networks. There is no supplied evidence of active exploitation, so response should be urgent and risk-based rather than emergency incident handling by default.
Technical view
A man-in-the-middle can send an invalid response at a specific protocol stage, causing Net::IMAP#starttls to return successfully without establishing TLS. Affected branches are below 0.3.10, 0.4.24, 0.5.14, and 0.6.4. The CVSS 4.0 score is 7.6, reflecting high confidentiality and integrity impact.
Likely exposure
Exposure is limited to Ruby applications using an affected net-imap version and invoking STARTTLS. Risk is greatest where an attacker can intercept or manipulate traffic between the application and IMAP server. Applications using patched versions are not identified as affected.
Exploitation context
The attack requires a network-positioned adversary, protocol timing, and an application initiating STARTTLS. The supplied record is not in KEV and provides no evidence of active exploitation. Public exploit availability is not established by the supplied sources.
Researcher notes
The flaw concerns erroneous state handling around invalid STARTTLS responses and response timing. Relevant weakness categories include missing cryptographic protection, error-handling failures, and improper sequencing. Review the branch-specific commits for exact behavioral changes. The supplied material establishes impact and patches but not real-world exploitation prevalence.
Mitigation direction
Upgrade net-imap to 0.3.10, 0.4.24, 0.5.14, 0.6.4, or a later compatible release.
Review vendor guidance for Ruby or operating-system packaged versions.
Prioritize applications carrying sensitive mail, credentials, or traffic across untrusted networks.
Investigate potentially exposed credentials if unencrypted IMAP sessions may have occurred.
Validation and detection
Inventory deployed and bundled net-imap versions, including transitive dependencies.
Identify application paths that call Net::IMAP#starttls.
Confirm production workloads load a patched version, not only an updated lockfile.
Test that STARTTLS failures cannot be reported as successful TLS establishment.
Verify affected systems actually negotiate TLS before exchanging sensitive IMAP data.
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.