← Back
CVE-2026-42577 high CVSS 7.5

Vulnerability in io.netty:netty-transport-native-epoll (CVE-2026-42577)

Summary

vulnerability in io.netty:netty-transport-native-epoll (CVE-2026-42577). Risk of unauthorized operations or information disclosure. Exploitable via ``ALLOW_HALF_CLOSURE``. Mitigation: upgrade to `4.2.13.Final` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-42577** has been found in io.netty:netty-transport-native-epoll. Attackers can target a specific entry point like ``ALLOW_HALF_CLOSURE`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10. What to do: upgrade io.netty:netty-transport-native-epoll to **4.2.13.Final** or later. If unsure, ask your IT team or search "io.netty:netty-transport-native-epoll CVE-2026-42577" on the vendor's site.
CVE-2026-42577 (io.netty:netty-transport-native-epoll) — CWE-772 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `ALLOW_HALF_CLOSURE` / `EPOLLERR` / `EPOLLHUP` / `channelInactive` Patched: `4.2.13.Final` — apply immediately Workaround: configure idle timeouts on connections to limit the lifetime of stale channels. 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-772) exists in io.netty:netty-transport-native-epoll. Attackers reach the vulnerable code path via ``ALLOW_HALF_CLOSURE`` without authentication.
📍 Affected scope
io.netty:netty-transport-native-epoll — . Attack surface: `ALLOW_HALF_CLOSURE` / `EPOLLERR` / `EPOLLHUP` / `channelInactive`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.2.13.Final**.
🛡️ Workaround
Workaround: configure idle timeouts on connections to limit the lifetime of stale channels.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.netty:netty-transport-native-epoll' .` 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 'io.netty:netty-transport-native-epoll' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate
    configure idle timeouts on connections to limit the lifetime of stale channels.

    パッチが適用されるまでの応急処置として、configure idle timeouts on connections to limit the lifetime of stale channels. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade io.netty:netty-transport-native-epoll to 4.2.13.Final

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

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

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

Affected packages

maven io.netty:netty-transport-native-epoll
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2.0.Final"},{"fixed":"4.2.13.Final"}]}]

References

🍪 About cookies

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

Details →