High, CVSS 8.1MavenAmendedPublished
netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
CVE-2026-61798 · GHSA-2mc4-j865-9q4r
- Affected
- Maven io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl <= 0.0.22.Final
- Fixed in
- 0.0.23.Final· Vendor fix available
- Issue
- io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl exposes raw HPKE private key bytes in string representations and error messages. BoringSSLAsymmetricCipherKeyPair.toString() includes the private-key parameter object, and BoringSSLAsymmetricKeyParameter.toString() renders the full byte array with Arrays.toString(bytes). Separately, failed native key initialization includes Arrays.toString(privateKeyBytes) in the thrown IllegalArgumentException message. Applications that log key-pair objects or exceptions can persist private key material in logs. Details codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAsymmetricCipherKeyPair.java renders private key material through toString(): - BoringSSLAsymmetricCipherKeyPair.toString() at lines 72-78 concatenates "privateKey=" + privateKey. - privateKey is a BoringSSLAsymmetricKeyParameter created with isPrivate=true at lines 26-36.…
Recommended action: Upgrade to 0.0.23.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.