netty-incubator-codec-ohttp information disclosure of HPKE private keys in logs
Only affects applications that log HPKE key-pair objects or initialization exceptions from io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl up to 0.0.22.Final. Fixed in netty-incubator-codec-ohttp 0.0.23.Final.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.23.Final
- Who is exposed
- Specific setups only
Summary
The netty-incubator-codec-ohttp library can write complete HPKE private key bytes into logs, telemetry, and exception messages. A remote attacker with low privileges and no user action needed can read those records, recover the private key, and undermine OHTTP message confidentiality and authenticity.
Written by a model
Original description
netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BoringSSLAsymmetricCipherKeyPair.toString in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAsymmetricCipherKeyPair.java includes its private parameter, BoringSSLAsymmetricKeyParameter.toString in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAsymmetricKeyParameter.java renders the complete private-key byte array when isPrivate is true, and BoringSSL.EVP_HPKE_KEY_init_or_throw in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSL.java includes rejected privateKeyBytes in an exception message. Applications that log affected key-pair objects or initialization exceptions can persist complete HPKE private key material in logs or telemetry. Anyone who can read those records can recover the key and may compromise OHTTP message confidentiality or authenticity expectations while the key remains usable. This issue is fixed in version 0.0.23.Final.
Who should check
Teams running netty-incubator-codec-ohttp up to 0.0.22.Final with the BoringSSL HPKE classes module that log key pairs or HPKE initialization exceptions
“io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl exposes raw HPKE private key bytes”
What to do
Check whether your setup matches what the bug needs.
Applications log key-pair objects or initialization exceptions from the BoringSSL HPKE classes module Affected package is io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl, versions up to 0.0.22.FinalUpgrade to a fixed version: 0.0.23.Final.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-61798 (netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-61798 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final
Fixed versions: 0.0.23.Final.
Conditions (all must be true for the bug to be hit):
- Applications log key-pair objects or initialization exceptions from the BoringSSL HPKE classes module (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r)
- Affected package is io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl, versions up to 0.0.22.Final (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-61798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61798 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r
- https://github.com/netty/netty-incubator-codec-ohttp/commit/2ad8eed90e3e47a23e46589b5c68463b4741c04c
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-61798
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61798"}.Affected versions
- netty netty-incubator-codec-ohttpfixed in 0.0.23.Final
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · netty/netty-incubator-codec-ohttp · Advisory GHSA-2mc4-j865-9q4r |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-61798 |
| Record | NVD · CVE-2026-61798 |
| Other links 2 | |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Commit 2ad8eed9 |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Release netty-incubator-codec-parent-ohttp-0.0.23.Final |
Questions about CVE-2026-61798
Is CVE-2026-61798 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The BoringSSL HPKE classes expose raw HPKE private key bytes through toString() and exception messages. If an application logs a key-pair object or an initialization exception, the private key material can be written to its logs, and anyone with access to those logs can recover the key.
Source: github.com, github.com
Which versions are affected by CVE-2026-61798?
netty-incubator-codec-ohttp: before 0.0.23.Final.
Source: cve.now feed data
Am I affected, and how do I check?
The affected package is io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl, versions up to 0.0.22.Final. Exposure requires that the application logs HPKE key-pair objects or initialization exceptions from these classes. To check a project, look at the version of that artifact in its dependencies and review whether its logging records those objects or exceptions.
Source: github.com, github.com
How do I fix CVE-2026-61798?
Upgrade netty-incubator-codec-ohttp to 0.0.23.Final, the fixed version. The advisory's fix reference is netty-incubator-codec-parent-ohttp-0.0.23.Final.
Source: github.com, github.com
Related
- CVE-2026-61827netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields
- CVE-2026-54251netty-incubator-codec-ohttp: [OHttpServerCodec] Native Direct-Memory Leak on AEAD Decryption Failure Leads to Gateway Denial of Service
- CVE-2024-40642Absent Input Validation in BinaryHttpParser in the netty incubator codec.bhttp
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
- CVE-2026-63124netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
- CVE-2026-41207netty-incubator-codec-ohttp's HPKEContext operations may produce empty byte[] on failures
No corrections so far. Something wrong on this page? Report an error.