Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-x43w-ph7m-pfjx

hexchat crate has a Use After Free vulnerability

Also known asRUSTSEC-2025-0153
Published
Feb 25, 2026
Updated
Feb 26, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

1 pkg affected
🦀hexchat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iohexchatall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hexchat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of hexchat has shipped for GHSA-x43w-ph7m-pfjx yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-x43w-ph7m-pfjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x43w-ph7m-pfjx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-x43w-ph7m-pfjx in your dependencies?

O3 detects GHSA-x43w-ph7m-pfjx across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.