Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.1

OpenMLS improper persistence of the secret tree during message processing

GHSA-qr9h-x63w-vqfm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openmls 0.7.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io openmls

    Affected
    <= 0.7.0
    Fixed in
    0.7.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.1 · 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 · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary A bug in the OpenMLS library prevented private key material from being updated in storage during message processing. The key material in question are the keys stored in the MLS secret tree, which are used for decryption of private MLS messages. The effects of the bug are limited in scope, but can affect forward secrecy and limit how many messages can be decrypted. Technical details Scope The scope of the bug is limited to private messages (application and handshake messages) received in groups. Furthermore, the scope is limited to one epoch and the effects are reset with each epoch transition, or through consecutive group operations without reloading group state in between. Functional impact Within each epoch of a group, there is a maximum number of private messages per sender that can be skipped before an error is thrown. The number of messages is set through maximumforwarddistance in the SenderRatchetConfiguration and the default value is 1000. The bug causes the library to…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-qr9h-x63w-vqfm

Agent brief

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

# Patch Next advisory brief: GHSA-qr9h-x63w-vqfm

Advisory: OpenMLS improper persistence of the secret tree during message processing
IDs: GHSA-qr9h-x63w-vqfm
Record: https://patchnext.com/advisories/ghsa-qr9h-x63w-vqfm (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openmls 0.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io openmls: affected <= 0.7.0; fixed in 0.7.1

## Suggested inspection (read-only)
- crates.io openmls: 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 openmls.
- 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-qr9h-x63w-vqfm (GitHub-reviewed advisory GHSA-qr9h-x63w-vqfm lists affected ranges: crates.io openmls >=0 <=0.7.0)

Commands are suggestions: review each one before running it.

Loading voting…