Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5

Data races in try-mutex

CVE-2020-35924GHSA-64j8-7gp2-xjx5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (try-mutex 0.3.0), 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 try-mutex

    Affected
    < 0.3.0
    Fixed in
    0.3.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2020-35924: 0.38% estimated exploitation activity in the next 30 days; percentile 32.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affected versions of this crate unconditionally implemented Sync trait for TryMutex<T type. This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race. The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait implementation.

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

    Published from ghsa record GHSA-64j8-7gp2-xjx5

Agent brief

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

# Patch Next advisory brief: CVE-2020-35924

Advisory: Data races in try-mutex
IDs: CVE-2020-35924, GHSA-64j8-7gp2-xjx5
Record: https://patchnext.com/advisories/cve-2020-35924 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: try-mutex 0.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io try-mutex: affected < 0.3.0; fixed in 0.3.0

## Suggested inspection (read-only)
- crates.io try-mutex: 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 try-mutex.
- 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-64j8-7gp2-xjx5 (GitHub-reviewed advisory GHSA-64j8-7gp2-xjx5 lists affected ranges: crates.io try-mutex >=0 <0.3.0)

Commands are suggestions: review each one before running it.

Loading voting…