What is GHSA-5X36-7567-3CW6?

GHSA-5X36-7567-3CW6 is a medium-severity out-of-bounds read vulnerability in partial_sort (rust), affecting versions < 0.2.0. It is fixed in 0.2.0. A read operation accesses a memory location beyond the intended buffer boundary.

Which versions of partial_sort are affected by GHSA-5X36-7567-3CW6?

partial_sort (rust) versions < 0.2.0 is affected.

Is there a fix for GHSA-5X36-7567-3CW6?

Yes. GHSA-5X36-7567-3CW6 is fixed in 0.2.0. Upgrade to this version or later.

Is GHSA-5X36-7567-3CW6 exploitable, and should I be worried?

Whether GHSA-5X36-7567-3CW6 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-5X36-7567-3CW6 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-5X36-7567-3CW6 in partial_sort

Q: Which versions of partial_sort are affected by GHSA-5X36-7567-3CW6?

partial_sort (rust) versions < 0.2.0 is affected.

Q: Is there a fix for GHSA-5X36-7567-3CW6?

Yes. GHSA-5X36-7567-3CW6 is fixed in 0.2.0. Upgrade to this version or later.

Q: Is GHSA-5X36-7567-3CW6 exploitable, and should I be worried?

Whether GHSA-5X36-7567-3CW6 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-5X36-7567-3CW6 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-5X36-7567-3CW6?

Upgrade partial_sort to 0.2.0 or later.

Summary

partial_sort contains Out-of-bounds Read in release mode

Affected versions of this crate were using a debug assertion to validate the last parameter of partial_sort(). This would allow invalid inputs to cause an out-of-bounds read instead of immediately panicking, when compiled without debug assertions.

All writes are bounds-checked, so the out-of-bounds memory access is read-only. This also means that the first attempted out-of-bounds write will panic, limiting the possible reads.

The accessible region is further limited by an initial bounds-checked read at (last / 2) - 1, i.e., it is proportional to the size of the vector.

This bug has been fixed in v0.2.0.

Impact

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

partial_sort (< 0.2.0)

Security releases

partial_sort → 0.2.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 partial_sort to 0.2.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-5X36-7567-3CW6? GHSA-5X36-7567-3CW6 is a medium-severity out-of-bounds read vulnerability in partial_sort (rust), affecting versions < 0.2.0. It is fixed in 0.2.0. A read operation accesses a memory location beyond the intended buffer boundary.
Which versions of partial_sort are affected by GHSA-5X36-7567-3CW6? partial_sort (rust) versions < 0.2.0 is affected.
Is there a fix for GHSA-5X36-7567-3CW6? Yes. GHSA-5X36-7567-3CW6 is fixed in 0.2.0. Upgrade to this version or later.
Is GHSA-5X36-7567-3CW6 exploitable, and should I be worried? Whether GHSA-5X36-7567-3CW6 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-5X36-7567-3CW6 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-5X36-7567-3CW6? Upgrade partial_sort to 0.2.0 or later.