Bug fixes in hpke-rs, hpke-rs-rust-crypto

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

We publish a GitHub security advisory for any releases whose CHANGELOG includes bug-fixes, and encourage our users to upgrade. The latest releases of the hpke-rs and hpke-rs-rust-crypto crates contain the following bug-fixes: hpke-rs - #127: Fix KemAlgorithm::TryFrom<u16 mapping where 0x004D incorrectly resolved to XWingDraft06 instead of XWingDraft06Obsolete. - #123: Fix potential overflow in context counter and switch to use u64. - #128: Return errors when trying to use open/seal with export only ciphersuite and when using kdf export with an output that's too long (instead of truncating it) The issue fixed in #123 was first reported by Nadim Kobeissi. The issues fixed in #127 and #128 were first reported by Scott Arciszewski. hpke-rs-rust-crypto - #124: Error out on x25519 0 keys The issue fixed in #124 was first reported by Nadim Kobeissi.

Published by the source

13 Feb 2026, 20:05 UTC

Last modified by the source

25 Mar 2026, 21:37 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g433-pq76-6cmf

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

# Patch Next advisory brief: GHSA-g433-pq76-6cmf

Advisory: Bug fixes in hpke-rs, hpke-rs-rust-crypto
IDs: GHSA-g433-pq76-6cmf
Record: https://patchnext.com/advisories/ghsa-g433-pq76-6cmf (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hpke-rs-rust-crypto 0.6.0; hpke-rs 0.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io hpke-rs-rust-crypto: affected < 0.6.0; fixed in 0.6.0
- crates.io hpke-rs: affected < 0.6.0; fixed in 0.6.0

## Suggested inspection (read-only)
- crates.io hpke-rs-rust-crypto: check the installed version with your package manager.
- crates.io hpke-rs: 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 hpke-rs-rust-crypto, hpke-rs.
- 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://github.com/advisories/GHSA-g433-pq76-6cmf (GitHub-reviewed advisory GHSA-g433-pq76-6cmf lists affected ranges: crates.io hpke-rs >=0 =0 <0.6.0)

Commands are suggestions: review each one before running it.