Which versions of slab are affected by CVE-2025-55159?

slab (rust) versions = 0.4.10 is affected.

Is there a fix for CVE-2025-55159?

Yes. CVE-2025-55159 is fixed in 0.4.11. Upgrade to this version or later.

Is CVE-2025-55159 exploitable, and should I be worried?

Whether CVE-2025-55159 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 CVE-2025-55159 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 CVE-2025-55159?

Upgrade slab to 0.4.11 or later.

CVE-2025-55159 in slab

CVE-2025-55159

CVE-2025-55159 is a medium-severity security vulnerability in slab (rust), affecting versions = 0.4.10. It is fixed in 0.4.11.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

slab allows out-of-bounds access in getdisjointmut due to incorrect bounds check

Workarounds

Avoid using get_disjoint_mut with indices that might be beyond the slab's actual length, or upgrade to v0.4.11 or later.

References

https://github.com/tokio-rs/slab/pull/152

Impact

The get_disjoint_mut method in slab v0.4.10 incorrectly checked if indices were within the slab's capacity instead of its length, allowing access to uninitialized memory. This could lead to undefined behavior or potential crashes.

Affected versions

slab (= 0.4.10)

Security releases

slab → 0.4.11 (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

This has been fixed in slab v0.4.11.

Frequently Asked Questions

What is CVE-2025-55159? CVE-2025-55159 is a medium-severity security vulnerability in slab (rust), affecting versions = 0.4.10. It is fixed in 0.4.11.
Which versions of slab are affected by CVE-2025-55159? slab (rust) versions = 0.4.10 is affected.
Is there a fix for CVE-2025-55159? Yes. CVE-2025-55159 is fixed in 0.4.11. Upgrade to this version or later.
Is CVE-2025-55159 exploitable, and should I be worried? Whether CVE-2025-55159 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 CVE-2025-55159 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 CVE-2025-55159? Upgrade slab to 0.4.11 or later.