Answer in brief
CVE-2026-61798 records a High severity (CVSS 8.1) vulnerability in netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages. The current sources do not mark it as known exploited. The current feed maps netty/netty-incubator-codec-ohttp (generic), io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (maven), io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps netty/netty-incubator-codec-ohttp (generic), io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (maven), io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| netty/netty-incubator-codec-ohttpgeneric | <0.0.23.Final | 0.0.23.Final |
| io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringsslmaven | >=0 <0.0.23.Final | 0.0.23.Final |
| io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringsslmaven | <=0.0.22.Final | 0.0.23.Final |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.