Summary
Insufficient covariance check makes self_cell unsound
All public versions prior to 1.02 used an insufficient check to ensure that users correctly marked the dependent type as either covariant or not_covariant. This allowed users to mark a dependent as covariant even though its type was not covariant but invariant, for certain invariant types involving trait object lifetimes. One example for such a dependent type is type Dependent<'a> = RefCell<Box<dyn fmt::Display + 'a>>. Such a type allowed unsound usage in purely safe user code that leads to undefined behavior. The patched versions now produce a compile time error if such a type is marked as covariant.
Impact
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
self_cell to 0.10.3 or later; self_cell to 1.0.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-48M6-WM5P-RR6H? GHSA-48M6-WM5P-RR6H is a high-severity security vulnerability in self_cell (rust), affecting versions < 0.10.3. It is fixed in 0.10.3, 1.0.2.
- Which versions of self_cell are affected by GHSA-48M6-WM5P-RR6H? self_cell (rust) versions < 0.10.3 is affected.
- Is there a fix for GHSA-48M6-WM5P-RR6H? Yes. GHSA-48M6-WM5P-RR6H is fixed in 0.10.3, 1.0.2. Upgrade to this version or later.
- Is GHSA-48M6-WM5P-RR6H exploitable, and should I be worried? Whether GHSA-48M6-WM5P-RR6H 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-48M6-WM5P-RR6H 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-48M6-WM5P-RR6H?
- Upgrade
self_cellto 0.10.3 or later - Upgrade
self_cellto 1.0.2 or later
- Upgrade