Summary
hexchat crate has a Use After Free vulnerability
All versions of this crate have function deregister_command which can result in use after free. This is unsound.
In addition, all versions since 0.3.0 have "safe" macros, which are documented as unsafe to use in threads.
In addition, the hexchat crate is no longer actively maintained. If users rely on this crate, consider switching to an alternative.
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
In the interim: Keep the dependency up to date. In native-code projects, use memory-safe data structures and address sanitizers during testing.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-X43W-PH7M-PFJX? GHSA-X43W-PH7M-PFJX is a high-severity use after free vulnerability in hexchat (rust), affecting versions <= 0.6.3. No fixed version is listed yet. Memory is accessed after it has been freed, leading to undefined behavior in native code.
- Which versions of hexchat are affected by GHSA-X43W-PH7M-PFJX? hexchat (rust) versions <= 0.6.3 is affected.
- Is there a fix for GHSA-X43W-PH7M-PFJX? No fixed version is listed for GHSA-X43W-PH7M-PFJX yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-X43W-PH7M-PFJX exploitable, and should I be worried? Whether GHSA-X43W-PH7M-PFJX 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-X43W-PH7M-PFJX 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-X43W-PH7M-PFJX? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use memory-safe data structures and address sanitizers during testing.