Categories
CVE-2026-41207 medium CVSS 5.3

Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-41207)

Summary

Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-41207). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.21.Final or later.

Original description

The description as published by the source.

HKDF_expand: returns non-NULL on failure. The byte[] is filled with zeros and has no way to distinguish success from failure. Since this output is used as HKDF key material for the response AEAD, a failure silently produces an all-zero key.

When EVP_HPKE_CTX_export fails it also returns an empty byte[] array filled with zeros. This byte[] feeds directly into OHttpCrypto.createResponseAEAD(...). A silent all-zero export secret would produce a deterministic, attacker-predictable AEAD key.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41207 has been found in io.netty.incubator:netty-incubator-codec-ohttp.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.21.Final or later.
If unsure, ask your IT team or search "io.netty.incubator:netty-incubator-codec-ohttp CVE-2026-41207" on the vendor's site.

CVE-2026-41207 (io.netty.incubator:netty-incubator-codec-ohttp) — CWE-330 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.0.21.Final — 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-330) exists in io.netty.incubator:netty-incubator-codec-ohttp.

📍 Affected scope

Check the vendor advisory for the affected versions of io.netty.incubator:netty-incubator-codec-ohttp.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.0.21.Final.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.netty.incubator:netty-incubator-codec-ohttp を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.21.Final

    ステージング環境で 0.0.21.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

maven io.netty.incubator:netty-incubator-codec-ohttp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.21.Final"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details