Skip to content
Fencer Intel
high —

GHSA-g433-pq76-6cmf json

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

published 9mo ago modified 7mo ago also RUSTSEC-2026-0069 , RUSTSEC-2026-0070 , RUSTSEC-2026-0071 , RUSTSEC-2026-0072

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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](https://github.com/cryspen/hpke-rs/pull/127): Fix `KemAlgorithm::TryFrom<u16>` mapping where `0x004D` incorrectly resolved to `XWingDraft06` instead of `XWingDraft06Obsolete`. - [#123](https://github.com/cryspen/hpke-rs/pull/123): Fix potential overflow in context counter and switch to use u64. - [#128](https://github.com/cryspen/hpke-rs/pull/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](https://github.com/cryspen/hpke-rs/pull/124): Error out on x25519 0 keys

The issue fixed in #124 was first reported by Nadim Kobeissi.

Patch / fix

Is GHSA-g433-pq76-6cmf in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io hpke-rs
<0.6.0
>=0.0.0-0, <0.6.0
0.6.0
crates.io hpke-rs-rust-crypto
<0.6.0
>=0.0.0-0, <0.6.0
0.6.0

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound
  • CWE-20 Improper Input Validation
  • CWE-697 Incorrect Comparison

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.