How severe is GHSA-x43w-ph7m-pfjx?

No CVSS score has been assigned to GHSA-x43w-ph7m-pfjx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x43w-ph7m-pfjx?

GHSA-x43w-ph7m-pfjx affects the following packages: hexchat (crates.io). Ecosystems affected: crates.io.

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

The records we use list no patched version of hexchat for GHSA-x43w-ph7m-pfjx. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-x43w-ph7m-pfjx in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hexchat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x43w-ph7m-pfjx if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-x43w-ph7m-pfjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-x43w-ph7m-pfjx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-x43w-ph7m-pfjx published, and has it been updated?

GHSA-x43w-ph7m-pfjx was published on February 25, 2026 and was last updated on February 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

hexchat crate has a Use After Free vulnerabilityGHSA-x43w-ph7m-pfjx

GHSA-x43w-ph7m-pfjx is a security vulnerability in hexchat. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0153

Published

Feb 25, 2026

Updated

Feb 26, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Feb 26, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hexchat`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hexchat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of hexchat for GHSA-x43w-ph7m-pfjx. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works