What is GHSA-M296-J53X-XV95?

GHSA-M296-J53X-XV95 is a high-severity race condition vulnerability in tiny_future (rust), affecting versions < 0.4.0. It is fixed in 0.4.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is GHSA-M296-J53X-XV95?

GHSA-M296-J53X-XV95 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of tiny_future are affected by GHSA-M296-J53X-XV95?

tiny_future (rust) versions < 0.4.0 is affected.

Is there a fix for GHSA-M296-J53X-XV95?

Yes. GHSA-M296-J53X-XV95 is fixed in 0.4.0. Upgrade to this version or later.

Is GHSA-M296-J53X-XV95 exploitable, and should I be worried?

Whether GHSA-M296-J53X-XV95 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-M296-J53X-XV95 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-M296-J53X-XV95 in tiny_future

Q: How severe is GHSA-M296-J53X-XV95?

GHSA-M296-J53X-XV95 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of tiny_future are affected by GHSA-M296-J53X-XV95?

tiny_future (rust) versions < 0.4.0 is affected.

Q: Is there a fix for GHSA-M296-J53X-XV95?

Yes. GHSA-M296-J53X-XV95 is fixed in 0.4.0. Upgrade to this version or later.

Q: Is GHSA-M296-J53X-XV95 exploitable, and should I be worried?

Whether GHSA-M296-J53X-XV95 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-M296-J53X-XV95 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-M296-J53X-XV95?

Upgrade tiny_future to 0.4.0 or later.

Summary

Data races in tiny_future

tiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit c791919 by adding trait bounds to Future's Send and Sync.

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

GHSA-M296-J53X-XV95 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.0); upgrading removes the vulnerable code path.

Affected versions

tiny_future (< 0.4.0)

Security releases

tiny_future → 0.4.0 (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 tiny_future to 0.4.0 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-M296-J53X-XV95? GHSA-M296-J53X-XV95 is a high-severity race condition vulnerability in tiny_future (rust), affecting versions < 0.4.0. It is fixed in 0.4.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is GHSA-M296-J53X-XV95? GHSA-M296-J53X-XV95 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of tiny_future are affected by GHSA-M296-J53X-XV95? tiny_future (rust) versions < 0.4.0 is affected.
Is there a fix for GHSA-M296-J53X-XV95? Yes. GHSA-M296-J53X-XV95 is fixed in 0.4.0. Upgrade to this version or later.
Is GHSA-M296-J53X-XV95 exploitable, and should I be worried? Whether GHSA-M296-J53X-XV95 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-M296-J53X-XV95 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-M296-J53X-XV95? Upgrade tiny_future to 0.4.0 or later.