CVE-2026-61798
| Severity | 8.1 High CVSS 3.1 |
|---|---|
| Fixed in | 0.0.23.Final |
| Weakness | Information exposure (CWE-200) |
| Published | 19 Nov 2026 |
Not yet in NVD's feed. The description, CVSS score and weakness below come from the organisation that issued the CVE. NVD hasn't analysed it yet, and its NVD page may not exist yet.
Published yesterday. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.
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.
CWE-312CWE-532
Exploitation status
No public exploit
No exploit has been reported in the sources we check.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment no assessment published
- Indexed PoC none indexed
- EPSS not scored
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists: netty/netty-incubator-codec-ohttp 2ad8eed.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all |
|---|---|
| Finding | This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious. |
| Candidate fix | https://github.com/netty/netty-incubator-codec-ohttp/commit/2ad8eed90e3e47a23e46589b5c68463b4741c04c : a commit: the change itself |
Affected software and releases
Maven packages
Affected and fixed versions, from OSV.dev| Package | Introduced | Fixed | Last affected |
|---|---|---|---|
io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl |
0 | 0.0.23.Final |
unbounded |
Products and versions
1 product, 1 version entry| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| osv | io.netty.incubator | netty-incubator-codec-ohttp-hpke-classes-boringssl | generic | < 0.0.23 |
References
Timeline
Timeline
| Published | 2026-11-19 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-11-19 | NVD's own last-modified date for this record. |