What is GHSA-W59H-378F-2FRM?

GHSA-W59H-378F-2FRM is a medium-severity security vulnerability in threadalone (rust), affecting versions < 0.2.1. It is fixed in 0.2.1.

Which versions of threadalone are affected by GHSA-W59H-378F-2FRM?

threadalone (rust) versions < 0.2.1 is affected.

Is there a fix for GHSA-W59H-378F-2FRM?

Yes. GHSA-W59H-378F-2FRM is fixed in 0.2.1. Upgrade to this version or later.

Is GHSA-W59H-378F-2FRM exploitable, and should I be worried?

Whether GHSA-W59H-378F-2FRM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-W59H-378F-2FRM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-W59H-378F-2FRM in threadalone

Q: Which versions of threadalone are affected by GHSA-W59H-378F-2FRM?

threadalone (rust) versions < 0.2.1 is affected.

Q: Is there a fix for GHSA-W59H-378F-2FRM?

Yes. GHSA-W59H-378F-2FRM is fixed in 0.2.1. Upgrade to this version or later.

Q: Is GHSA-W59H-378F-2FRM exploitable, and should I be worried?

Whether GHSA-W59H-378F-2FRM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-W59H-378F-2FRM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-W59H-378F-2FRM?

Upgrade threadalone to 0.2.1 or later.

Summary

Unsound sending of non-Send types across threads in threadalone

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. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.

Impact

Affected versions

threadalone (< 0.2.1)

Security releases

threadalone → 0.2.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade threadalone to 0.2.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-W59H-378F-2FRM? GHSA-W59H-378F-2FRM is a medium-severity security vulnerability in threadalone (rust), affecting versions < 0.2.1. It is fixed in 0.2.1.
Which versions of threadalone are affected by GHSA-W59H-378F-2FRM? threadalone (rust) versions < 0.2.1 is affected.
Is there a fix for GHSA-W59H-378F-2FRM? Yes. GHSA-W59H-378F-2FRM is fixed in 0.2.1. Upgrade to this version or later.
Is GHSA-W59H-378F-2FRM exploitable, and should I be worried? Whether GHSA-W59H-378F-2FRM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-W59H-378F-2FRM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-W59H-378F-2FRM? Upgrade threadalone to 0.2.1 or later.