PT-2026-80781 · Unknown · Netty-Incubator-Codec-Ohttp-Hpke-Classes-Boringssl
CVE-2026-61798
·
Published
2026-07-12
·
Updated
2026-08-20
CVSS v2.0
8.5
High
| Vector | AV:N/AC:L/Au:S/C:C/I:C/A:N |
Name of the Vulnerable Software and Affected Versions
io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (affected versions not specified)
Description
An information disclosure issue exists where raw HPKE private key bytes are exposed in string representations and error messages. Specifically, the
BoringSSLAsymmetricCipherKeyPair.toString() function includes the private-key parameter object, and the BoringSSLAsymmetricKeyParameter.toString() function renders the full byte array. Additionally, when native key initialization fails, the EVP HPKE KEY init or throw() function includes the privateKeyBytes in the IllegalArgumentException message. Since logging frameworks often call toString() or record exception messages, sensitive private key material can be persisted in logs or telemetry, allowing an attacker with log access to recover the keys and compromise the confidentiality and integrity of OHTTP messages.Recommendations
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
- Redact private key material in
BoringSSLAsymmetricKeyParameter.toString()whenisPrivateis true. - Redact the
privateKeyinBoringSSLAsymmetricCipherKeyPair.toString(). - Remove
privateKeyBytesfrom the exception message inBoringSSL.EVP HPKE KEY init or throw(). - Avoid logging key-pair objects or exceptions that may contain sensitive key material.
Information Disclosure
Cleartext Storage of Sensitive Information
Insertion into Log File
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Netty-Incubator-Codec-Ohttp-Hpke-Classes-Boringssl