← Back
CVE-2026-48040
critical
CVSS 9.1
Out-of-Bounds Read in io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl (CVE-2026-48040)
Summary
vulnerability in io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl (CVE-2026-48040). Confidential information can be exposed externally. Exploitable via ``sun.misc.Unsafe``. Mitigation: upgrade to `0.0.22.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48040** has been found in io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl.
Attackers can target a specific entry point like ``sun.misc.Unsafe`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl to **0.0.22.Final** or later.
If unsure, ask your IT team or search "io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl CVE-2026-48040" on the vendor's site.
CVE-2026-48040 (io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl) — CWE-125 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `sun.misc.Unsafe` / `PooledByteBufAllocator` / `PooledDirectByteBuf`
Patched: `0.0.22.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
**out-of-bounds read** (CWE-125) exists in io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl. Attackers reach the vulnerable code path via ``sun.misc.Unsafe`` without authentication.
📍 Affected scope
io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl — . Attack surface: `sun.misc.Unsafe` / `PooledByteBufAllocator` / `PooledDirectByteBuf`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.22.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. Run `grep -r 'io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl' .` 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
-
1Identify exposure identify
grep -r 'io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl to 0.0.22.Finalステージング環境で 0.0.22.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.netty.incubator:netty-incubator-codec-ohttp-hpke-native-boringssl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.22.Final"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-48040
- package https://github.com/netty/netty-incubator-codec-ohttp
- web https://github.com/netty/netty-incubator-codec-ohttp/commit/7ad38d5cc2827af7e067e5c1e1ac37cd4566dad9
- web https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-32hf-8jw3-v4qq
- web https://github.com/advisories/GHSA-32hf-8jw3-v4qq