Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

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

CVE-2026-61798GHSA-2mc4-j865-9q4r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl 0.0.23.Final), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary 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.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2mc4-j865-9q4r

  2. Revision 1 · created ·

    Published from osv record GHSA-2mc4-j865-9q4r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61798

Advisory: netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
IDs: CVE-2026-61798, GHSA-2mc4-j865-9q4r
Record: https://patchnext.com/advisories/cve-2026-61798 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl 0.0.23.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl: affected <= 0.0.22.Final; fixed in 0.0.23.Final

## Suggested inspection (read-only)
- Maven io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2mc4-j865-9q4r (OSV record GHSA-2mc4-j865-9q4r lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl >=0 <0.0.23.Final (fixed))
- Verified: https://github.com/advisories/GHSA-2mc4-j865-9q4r (GitHub-reviewed advisory GHSA-2mc4-j865-9q4r lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-ohttp-hpke-classes-boringssl >=0 <=0.0.22.Final)

Commands are suggestions: review each one before running it.

Loading voting…