hexchat crate has a Use After Free vulnerability
Priority LOW 38CWE-416Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | hexchat (crates.io) | up to 0.6.3 | — | No fix listed | GHSA-x43w-ph7m-pfjx |
- hexchat (crates.io) Vendor— Affected up to 0.6.3 Fixed in — No fix listed GHSA-x43w-ph7m-pfjx
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-x43w-ph7m-pfjx
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences