Summary
Use-after-free when setting the locale
Version 3.0.0 introduced an AtomicStr type, that is used to store the current locale. It stores the locale as a raw pointer to an Arc<String>. The locale can be read with AtomicStr::as_str(). AtomicStr::as_str() does not increment the usage counter of the Arc.
If the locale is changed in one thread, another thread can have a stale -- possibly already freed -- reference to the stored string.
Impact
Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.
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
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-C8V3-JHV9-4PPC? GHSA-C8V3-JHV9-4PPC is a medium-severity use after free vulnerability in rust-i18n-support (rust), affecting versions >= 3.0.0, < 3.0.1. It is fixed in 3.0.1. Memory is accessed after it has been freed, leading to undefined behavior in native code.
- Which versions of rust-i18n-support are affected by GHSA-C8V3-JHV9-4PPC? rust-i18n-support (rust) versions >= 3.0.0, < 3.0.1 is affected.
- Is there a fix for GHSA-C8V3-JHV9-4PPC? Yes. GHSA-C8V3-JHV9-4PPC is fixed in 3.0.1. Upgrade to this version or later.
- Is GHSA-C8V3-JHV9-4PPC exploitable, and should I be worried? Whether GHSA-C8V3-JHV9-4PPC 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-C8V3-JHV9-4PPC 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-C8V3-JHV9-4PPC? Upgrade
rust-i18n-supportto 3.0.1 or later.