← Back
CVE-2026-47241

Vulnerability in net-imap (CVE-2026-47241)

Summary

vulnerability in net-imap (CVE-2026-47241). Risk of unauthorized operations or information disclosure. Exploitable via ``criteria``. Mitigation: upgrade to `0.5.15` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-47241** has been found in net-imap. Attackers can target a specific entry point like ``criteria`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade net-imap to **0.5.15** or later. If unsure, ask your IT team or search "net-imap CVE-2026-47241" on the vendor's site.
CVE-2026-47241 (net-imap) — CWE-162 / Attack surface: `criteria` / `attr` / `search_keys` / `BAD` Patched: `0.5.15` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-162) exists in net-imap. Attackers reach the vulnerable code path via ``criteria`` without authentication.
📍 Affected scope
net-imap — . Attack surface: `criteria` / `attr` / `search_keys` / `BAD`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.5.15**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'net-imap' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'net-imap' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `net-imap` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade net-imap to 0.5.15

    ステージング環境で 0.5.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

rubygems net-imap
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.15"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →