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

Advisory record · `GHSA-g433-pq76-6cmf`

- **Identifiers:** `GHSA-g433-pq76-6cmf` · `RUSTSEC-2026-0069` · `RUSTSEC-2026-0070` · `RUSTSEC-2026-0071` · `RUSTSEC-2026-0072`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-190](https://cwe.mitre.org/data/definitions/190.html) · [CWE-697](https://cwe.mitre.org/data/definitions/697.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-697](https://agentprime.io/advisories/tag/cwe-697.md)
- **Published:** 13 Feb 2026
- **Updated:** 25 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Feb 2026, 20:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `hpke-rs` (crates.io): affected `<0.6.0`; fixed in `0.6.0`
- `hpke-rs-rust-crypto` (crates.io): affected `<0.6.0`; fixed in `0.6.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `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`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g433-pq76-6cmf)

## Sources

- [GitHub Advisory Database: GHSA-g433-pq76-6cmf](https://github.com/advisories/GHSA-g433-pq76-6cmf)
- [OSV: GHSA-g433-pq76-6cmf](https://osv.dev/vulnerability/GHSA-g433-pq76-6cmf)
- <https://github.com/cryspen/hpke-rs/security/advisories/GHSA-g433-pq76-6cmf>
- <https://github.com/cryspen/hpke-rs/pull/123>
- <https://github.com/cryspen/hpke-rs/pull/124>
- <https://github.com/cryspen/hpke-rs/pull/127>
- <https://github.com/cryspen/hpke-rs/pull/128>
- <https://github.com/cryspen/hpke-rs/commit/1c247b5c9aeca602ad2971c9bd49817fe2c308e6>
- <https://github.com/cryspen/hpke-rs/commit/25248bd624cc0325c98a05c169a0c9aa0aced632>
- <https://github.com/cryspen/hpke-rs/commit/3a8254938f43bdc4e0c9c4f987f8071f19779066>
- <https://github.com/cryspen/hpke-rs/commit/b54c8bb83906331bdf4f606cafa30cd7fd20b531>
- <https://github.com/cryspen/hpke-rs>
- <https://rustsec.org/advisories/RUSTSEC-2026-0070.html>
- <https://rustsec.org/advisories/RUSTSEC-2026-0072.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g433-pq76-6cmf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g433-pq76-6cmf/>. Everything for agents: <https://agentprime.io/llms.txt>.
