How severe is GHSA-h7h7-6mx3-r89v?

No CVSS score has been assigned to GHSA-h7h7-6mx3-r89v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h7h7-6mx3-r89v?

GHSA-h7h7-6mx3-r89v affects the following packages: fyrox-core (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-h7h7-6mx3-r89v?

Update fyrox-core to 0.36 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h7h7-6mx3-r89v is resolved across your whole dependency graph.

How do I detect GHSA-h7h7-6mx3-r89v in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fyrox-core. 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.

How do I mitigate GHSA-h7h7-6mx3-r89v 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.

How does O3 Security protect against GHSA-h7h7-6mx3-r89v?

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

Is GHSA-h7h7-6mx3-r89v actively exploited in the wild?

No public exploit code has been indexed for GHSA-h7h7-6mx3-r89v 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-h7h7-6mx3-r89v published, and has it been updated?

GHSA-h7h7-6mx3-r89v was published on February 14, 2025 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

GHSA-h7h7-6mx3-r89v

Fyrox has unsound usages of `Vec::from_raw_parts`

Also known asRUSTSEC-2024-0435

Published

Feb 14, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀fyrox-core

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 public safe API transmute_vec_as_bytes, which incorrectly assumes that any generic type T could have stable layout, causing to uninitialized memory exposure if the users pass any types with padding bytes as T and cast it to u8 pointer.

In the issue, we develop a PoC to show passing struct type to transmute_vec_as_bytes could lead to undefined behavior with Vec::from_raw_parts.

The developers provide a patch by changing trait of Copy to Pod, which can make sure T should be plain data. This was patched in the latest version of master branch, but still not on the latest release (0.28.1).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`fyrox-core`	≥ 0.28.1&&< 0.36	0.36

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fyrox-core. 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.
Fix
Update fyrox-core to 0.36 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h7h7-6mx3-r89v is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-h7h7-6mx3-r89v 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-h7h7-6mx3-r89v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The library provides a public safe API `transmute_vec_as_bytes`, which incorrectly assumes that any generic type `T` could have stable layout, causing to uninitialized memory exposure if the users pass any types with padding bytes as `T` and cast it to `u8` pointer. In the [issue](https://github.com/FyroxEngine/Fyrox/issues/630), we develop a PoC to show passing struct type to `transmute_vec_as_bytes` could lead to undefined behavior with `Vec::from_raw_parts`. The developers provide a patch by changing trait of `Copy` to `Pod`, which can make sure `T` should be plain data. This was patc

O3 Security · Impact-Aware SCA

Is GHSA-h7h7-6mx3-r89v in your dependencies?

O3 detects GHSA-h7h7-6mx3-r89v 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.

Scan my dependencies How O3 SCA works