How severe is GHSA-g433-pq76-6cmf?

No CVSS score has been assigned to GHSA-g433-pq76-6cmf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g433-pq76-6cmf?

GHSA-g433-pq76-6cmf affects the following packages: hpke-rs (crates.io), hpke-rs-rust-crypto (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-g433-pq76-6cmf?

Update hpke-rs to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g433-pq76-6cmf is resolved across your whole dependency graph.

How do I detect GHSA-g433-pq76-6cmf in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hpke-rs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g433-pq76-6cmf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g433-pq76-6cmf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g433-pq76-6cmf can be triaged on real exposure rather than presence alone.

Is GHSA-g433-pq76-6cmf actively exploited in the wild?

No public exploit code has been indexed for GHSA-g433-pq76-6cmf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g433-pq76-6cmf published, and has it been updated?

GHSA-g433-pq76-6cmf was published on February 13, 2026 and was last updated on March 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-g433-pq76-6cmf — hpke-rs

Fix: cryspen/hpke-rs#123

GHSA-g433-pq76-6cmf is a remote code execution vulnerability in hpke-rs. A fix is available for hpke-rs — see the affected versions and patch details below.

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

Also known asRUSTSEC-2026-0069RUSTSEC-2026-0070RUSTSEC-2026-0071RUSTSEC-2026-0072

Published

Feb 13, 2026

Updated

Mar 25, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀hpke-rs🦀hpke-rs-rust-crypto

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hpke-rs`	all versions	0.6.0`cargo update -p hpke-rs --precise 0.6.0`
🦀crates.io	`hpke-rs-rust-crypto`	all versions	0.6.0`cargo update -p hpke-rs-rust-crypto --precise 0.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hpke-rs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hpke-rs to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g433-pq76-6cmf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g433-pq76-6cmf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g433-pq76-6cmf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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): Re

O3 Security · Impact-Aware SCA

Is GHSA-g433-pq76-6cmf in your dependencies?

O3 Security finds GHSA-g433-pq76-6cmf across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works