How severe is GHSA-h6xm-c6r4-vmwf?

No CVSS score has been assigned to GHSA-h6xm-c6r4-vmwf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h6xm-c6r4-vmwf?

GHSA-h6xm-c6r4-vmwf affects the following packages: spl-token-swap (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-h6xm-c6r4-vmwf?

The records we use list no patched version of spl-token-swap for GHSA-h6xm-c6r4-vmwf. 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-h6xm-c6r4-vmwf in my crates.io dependencies?

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

How do I mitigate GHSA-h6xm-c6r4-vmwf if there is no patch (or I can't update yet)?

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.

Is GHSA-h6xm-c6r4-vmwf actively exploited in the wild?

No public exploit code has been indexed for GHSA-h6xm-c6r4-vmwf 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-h6xm-c6r4-vmwf published, and has it been updated?

GHSA-h6xm-c6r4-vmwf was published on December 23, 2024 and was last updated on October 28, 2025. 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

Unsound usages of `u8` type casting in spl-token-swapGHSA-h6xm-c6r4-vmwf

GHSA-h6xm-c6r4-vmwf is a security vulnerability in spl-token-swap. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2024-0426

Published

Dec 23, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀spl-token-swap

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

The library provides a safe public API unpack to cast u8 array to arbitrary types, which can cause to undefined behaviors. The length check of array can only prevent out-of-bound access on the return type. However, it can't prevent misaligned pointer when casting u8 pointer to a type aligned to larger bytes. For example, if we assign u16 to T, misaligned raw pointer dereference could happen and cause to panic. Even if we pass the type aligned to same byte as u8 (e.g., bool), it could construct a illegal type since bool can only have 0 or 1 as bit patterns, which is also an undefined behavior. The further exploits of the bug here are still not clear, so we would report this issue as unsound.

The details of PoC to reproduce undefined behavior are provided in the issue.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`spl-token-swap`	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 spl-token-swap, 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 spl-token-swap for GHSA-h6xm-c6r4-vmwf. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

The library provides a safe public API `unpack` to cast `u8` array to arbitrary types, which can cause to undefined behaviors. The length check of array can only prevent out-of-bound access on the return type. However, it can't prevent misaligned pointer when casting `u8` pointer to a type aligned to larger bytes. For example, if we assign `u16` to `T`, **misaligned raw pointer dereference** could happen and cause to panic. Even if we pass the type aligned to same byte as `u8` (e.g., `bool`), it could construct a illegal type since `bool` can only have 0 or 1 as bit patterns, which is also an

O3 Security · Impact-Aware SCA

Is GHSA-h6xm-c6r4-vmwf in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works