matrix-sdk-crypto's UserIdentity::is_verified not checking verification status of own user identity while performing the check

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-40648: 0.28% estimated exploitation activity in the next 30 days; percentile 20.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The UserIdentity::isverified() method in the matrix-sdk-crypto crate before version 0.7.2 doesn't take into account the verification status of the user's own identity while performing the check and may as a result return a value contrary to what is implied by its name and documentation. Impact If the method is used to decide whether to perform sensitive operations towards a user identity, a malicious homeserver could manipulate the outcome in order to make the identity appear trusted. This is not a typical usage of the method, which lowers the impact. The method itself is not used inside the matrix-sdk-crypto crate. Patches The 0.7.2 release of the matrix-sdk-crypto crate includes a fix. Workarounds None.

Published by the source

18 Jul 2024, 15:28 UTC

Last modified by the source

8 Aug 2024, 05:08 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4qg4-cvh2-crgg

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

# Patch Next advisory brief: CVE-2024-40648

Advisory: matrix-sdk-crypto's `UserIdentity::is_verified` not checking verification status of own user identity while performing the check
IDs: CVE-2024-40648, GHSA-4qg4-cvh2-crgg
Record: https://patchnext.com/advisories/cve-2024-40648 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: matrix-sdk-crypto 0.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io matrix-sdk-crypto: affected < 0.7.2; fixed in 0.7.2

## Suggested inspection (read-only)
- crates.io matrix-sdk-crypto: 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 matrix-sdk-crypto.
- 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-4qg4-cvh2-crgg (GitHub-reviewed advisory GHSA-4qg4-cvh2-crgg lists affected ranges: crates.io matrix-sdk-crypto >=0 <0.7.2)

Commands are suggestions: review each one before running it.