cve.bz

CVE-2026-61798 netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages

8.1 highFix available

High (8.1) in netty netty-incubator-codec-ohttp. Fixed in io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl 0.0.23.Final.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CWEs
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-312 Cleartext Storage of Sensitive Information
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design, A09:2025 Logging & Alerting Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl (Maven): fixed in 0.0.23.Final

Ask an AI about this CVE

Show the promptExplain CVE-2026-61798 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61798?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61798?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61798 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
netty-incubator-codec-ohttp< 0.0.23.Final

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2mc4-j865-9q4rMavenio.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl<0.0.23.Final0.0.23.Final

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High
  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON