Rust advisories / hexchat
Unsound HighRUSTSEC-2025-0153 · hexchat
RUSTSEC-2025-0153: hexchat crate is unsound and unmaintained
Short answerhexchat has an API that can cause undefined behaviour from safe code: hexchat crate is unsound and unmaintained. No fixed version yet.
| Crate | hexchat |
|---|---|
| Type | Unsound (memory-corruption, memory-exposure) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High (GitHub rating) |
| Published | 2025-11-17 |
| Last changed | 2026-02-26 |
| Also known as | GHSA-x43w-ph7m-pfjx |
What to do
- Find who pulls it in:
cargo tree -i hexchat. - Avoid the affected API, or replace the crate.
Details from the advisory
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 you rely on this crate, consider switching to an alternative.
References
- Package: crates.io/crates/hexchat
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0153.html
- Report: github.com/pie-flavor/hexchat-rs/issues/3
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?