# GHSA-x43w-ph7m-pfjx: hexchat crate has a Use After Free vulnerability

> The hexchat Rust crate contains a use-after-free vulnerability in command deregistration, potentially allowing code execution or crashes; users should migrate to maintained alternatives.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Also known as:** RUSTSEC-2025-0153

## What is GHSA-x43w-ph7m-pfjx?

GHSA-x43w-ph7m-pfjx is an use after free vulnerability in hexchat, published on 17 Nov 2025. 

### Official description

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.

## Which versions are affected by GHSA-x43w-ph7m-pfjx?

3 open source packages ship an affected version, including hexchat.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hexchat` | crates.io | All versions to 0.6.3 | None |
| `hexchat` | crates.io | All versions to 0.6.3 | None |
| `hexchat` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-x43w-ph7m-pfjx?

No fix has been published for GHSA-x43w-ph7m-pfjx yet. Limit exposure of the affected software until one is available.

## Is GHSA-x43w-ph7m-pfjx being exploited?

There is no known exploitation of GHSA-x43w-ph7m-pfjx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x43w-ph7m-pfjx and fix it if it is affected.

What it is: GHSA-x43w-ph7m-pfjx is an use after free vulnerability in hexchat, published on 17 Nov 2025. 
Exploitation: There is no known exploitation of GHSA-x43w-ph7m-pfjx in the wild and no public exploit code.

Affected packages and fixed versions:
- hexchat (crates.io): affected all versions up to 0.6.3; no fix listed
- hexchat (crates.io): affected all versions up to 0.6.3; no fix listed
- hexchat (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-x43w-ph7m-pfjx/ (Markdown: https://insights.sbomify.com/GHSA-x43w-ph7m-pfjx/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x43w-ph7m-pfjx

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x43w-ph7m-pfjx/
Summaries are generated and may contain mistakes; the official description above is the record.