Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Unsound sending of non-Send types across threads in threadalone

GHSA-w59h-378f-2frm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (threadalone 0.2.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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Affected versions can run the Drop impl of a non-Send type on a different thread than it was created on. The flaw occurs when a stderr write performed by the threadalone crate fails, for example because stderr is redirected to a location on a filesystem that is full, or because stderr is a pipe that has been closed by the reader. Dropping a non-Send type on the wrong thread is unsound. If used with a type such as a pthread-based MutexGuard, [the consequence is undefined behavior][mutexguard]. If used with Rc, there would be a data race on the reference count, which is likewise undefined behavior. [mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326

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

    Published from ghsa record GHSA-w59h-378f-2frm

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-w59h-378f-2frm

Advisory: Unsound sending of non-Send types across threads in threadalone
IDs: GHSA-w59h-378f-2frm
Record: https://patchnext.com/advisories/ghsa-w59h-378f-2frm (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: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: threadalone 0.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io threadalone: affected < 0.2.1; fixed in 0.2.1

## Suggested inspection (read-only)
- crates.io threadalone: 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 threadalone.
- 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-w59h-378f-2frm (GitHub-reviewed advisory GHSA-w59h-378f-2frm lists affected ranges: crates.io threadalone >=0 <0.2.1)

Commands are suggestions: review each one before running it.

Loading voting…