Is net-imap 0.4 vulnerable?
RubyGems · 27 releases from 0.4.0 to 0.4.25 · latest net-imap is 0.6.8 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. net-imap 0.4.25, the last 0.4 release, is affected by 3 known security advisories (2 medium, 1 low), including CVE-2026-47242, CVE-2026-47240, CVE-2026-47241. 7 more affect earlier 0.4.x releases. Upgrade to 0.5.15 or later to fix all of them.
bundle update --conservative net-imap # Gemfile: '>= 0.5.15'Is your project on an affected net-imap?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting net-imap 0.4.25
Net::IMAP: Command Injection via ID command argument
- Affected
- >=0.6.0 <0.6.4.1 · <0.5.15
- Fixed in
- 0.5.15, 0.6.4.1
Net::IMAP: Denial of Service via incomplete raw argument validation
- Affected
- >=0.6.0 <0.6.4.1 · <0.5.15
- Fixed in
- 0.5.15, 0.6.4.1
Net::IMAP: Command Injection via non-synchronizing literal in "raw" argument
- Affected
- >=0.6.0 <0.6.4.1 · <0.5.15
- Fixed in
- 0.5.15, 0.6.4.1
Fixed within 0.4.x, affecting earlier releases
net-imap vulnerable to command Injection via "raw" arguments to multiple commands
- Affected
- >=0.6.0 <0.6.4 · >=0.5.0 <0.5.14 · <0.4.24
- Fixed in
- 0.4.24, 0.5.14, 0.6.4
net-imap vulnerable to command Injection via unvalidated Symbol inputs
- Affected
- >=0.6.0 <0.6.4 · >=0.5.0 <0.5.14 · <0.4.24
- Fixed in
- 0.4.24, 0.5.14, 0.6.4
net-imap vulnerable to denial of service via high iteration count for `SCRAM-*` authentication
- Affected
- >=0.6.0 <0.6.4 · >=0.5.0 <0.5.14 · >=0.4.0 <0.4.24
- Fixed in
- 0.4.24, 0.5.14, 0.6.4
net-imap has quadratic complexity when reading response literals
- Affected
- >=0.6.0 <0.6.4 · >=0.5.0 <0.5.14 · <0.4.24
- Fixed in
- 0.4.24, 0.5.14, 0.6.4
net-imap vulnerable to STARTTLS stripping via invalid response timing
- Affected
- >=0.6.0 <0.6.4 · >=0.5.0 <0.5.14 · >=0.4.0 <0.4.24 · <0.3.10
- Fixed in
- 0.3.10, 0.4.24, 0.5.14, 0.6.4
net-imap rubygem vulnerable to possible DoS by memory exhaustion
- Affected
- >=0.5.0 <0.5.7 · >=0.4.0 <0.4.20 · >=0.3.0 <0.3.9 · <0.2.5
- Fixed in
- 0.2.5, 0.3.9, 0.4.20, 0.5.7
Possible DoS by memory exhaustion in net-imap
- Affected
- >=0.3.2 <0.3.8 · >=0.4.0 <0.4.19 · >=0.5.0 <0.5.6
- Fixed in
- 0.3.8, 0.4.19, 0.5.6
Every net-imap 0.4.x release
Affected: 0.4.0 to 0.4.25. Latest net-imap: 0.6.8.
| Version | Known advisories |
|---|---|
| net-imap 0.4.25 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240 |
| net-imap 0.4.24 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240 |
| net-imap 0.4.23 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246 |
| net-imap 0.4.22 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246 |
| net-imap 0.4.21 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246 |
| net-imap 0.4.20 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246 |
| net-imap 0.4.19 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857 |
| net-imap 0.4.18 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.17 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.16 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.15 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.14 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.13 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.12 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.11 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.10 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.9.1 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.9 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.8 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.7 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.6 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.5 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.4 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.3 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.2 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.1 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
| net-imap 0.4.0 | CVE-2026-47242, CVE-2026-47241, CVE-2026-47240, CVE-2026-42257, CVE-2026-42258, CVE-2026-42256, CVE-2026-42245, CVE-2026-42246, CVE-2025-43857, CVE-2025-25186 |
Which of your client projects are still on net-imap 0.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact net-imap version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other net-imap versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.