# OpenMLS improper persistence of the secret tree during message processing

Advisory record · `GHSA-qr9h-x63w-vqfm`

- **Identifiers:** `GHSA-qr9h-x63w-vqfm`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 26 Sept 2025
- **Updated:** 26 Sept 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Sept 2025, 15:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `openmls` (crates.io): affected `<0.7.1`; fixed in `0.7.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The openmls crate, versions before 0.7.1, does not correctly persist the secret tree keys used to decrypt private MLS messages during message processing. An attacker who gains access to a client's stored state can decrypt up to maximum_forward_distance (default 1000) additional messages per sender in the current epoch, weakening forward secrecy. Upgrade to openmls 0.7.1 or later; state written before patching remains affected until the client enters a new epoch or the retention window passes.

Written 8 Nov 2026.

## 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:L/AC:H/AT:N/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

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

## Timeline

- 31 Oct 2026, 15:19 UTC: First seen by agentprime
- 31 Oct 2026, 15:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qr9h-x63w-vqfm)

## Sources

- [GitHub Advisory Database: GHSA-qr9h-x63w-vqfm](https://github.com/advisories/GHSA-qr9h-x63w-vqfm)
- [OSV: GHSA-qr9h-x63w-vqfm](https://osv.dev/vulnerability/GHSA-qr9h-x63w-vqfm)
- <https://github.com/openmls/openmls/security/advisories/GHSA-qr9h-x63w-vqfm>
- <https://github.com/openmls/openmls/commit/c73a074c804b30bec8284ac1e69a71b01db982ea>
- <https://github.com/openmls/openmls>

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-qr9h-x63w-vqfm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qr9h-x63w-vqfm/>. Everything for agents: <https://agentprime.io/llms.txt>.
