Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-54251)
Summary
Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-54251). Risk of unauthorized operations or information disclosure. Exploitable via ByteBuf. Mitigation: upgrade to 0.0.23.Final or later.
Original description
The description as published by the source.
The netty-incubator-codec-ohttp library implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty's ByteBuf memory management. When an OHTTP gateway processes encrypted client requests, it allocates a pooled direct (native off-heap) ByteBuf to hold the decrypted plaintext before the AEAD tag is verified. If the AEAD tag check fails — meaning the ciphertext is invalid — the decryption method throws a CryptoException, but the allocated buffer is never released because no try/finally block guards the allocation.
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-54251 has been found in io.netty.incubator:netty-incubator-codec-ohttp.
Attackers can target a specific entry point like ByteBuf over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.23.Final or later.
If unsure, ask your IT team or search "io.netty.incubator:netty-incubator-codec-ohttp CVE-2026-54251" on the vendor's site.
CVE-2026-54251 (io.netty.incubator:netty-incubator-codec-ohttp) — CWE-664
Attack surface: ByteBuf / CryptoException
Patched: 0.0.23.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.
A vulnerability (CWE-664) exists in io.netty.incubator:netty-incubator-codec-ohttp. Attackers reach the vulnerable code path via ByteBuf.
Check the vendor advisory for the affected versions of io.netty.incubator:netty-incubator-codec-ohttp. Attack surface: ByteBuf / CryptoException.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.23.Final.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.netty.incubator:netty-incubator-codec-ohttp を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.23.Finalステージング環境で 0.0.23.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com