How severe is GHSA-f7qj-v3vp-4856?

No CVSS score has been assigned to GHSA-f7qj-v3vp-4856 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f7qj-v3vp-4856?

GHSA-f7qj-v3vp-4856 affects the following packages: libafl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-f7qj-v3vp-4856?

Update libafl to 0.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7qj-v3vp-4856 is resolved across your whole dependency graph.

How do I detect GHSA-f7qj-v3vp-4856 in my crates.io dependencies?

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

How do I mitigate GHSA-f7qj-v3vp-4856 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-f7qj-v3vp-4856?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f7qj-v3vp-4856 can be triaged on real exposure rather than presence alone.

Is GHSA-f7qj-v3vp-4856 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f7qj-v3vp-4856 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-f7qj-v3vp-4856 published, and has it been updated?

GHSA-f7qj-v3vp-4856 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

GHSA-f7qj-v3vp-4856 — libafl

Fix: AFLplusplus/LibAFL#1530

GHSA-f7qj-v3vp-4856 is a security vulnerability in libafl. A fix is available for libafl — see the affected versions and patch details below.

libafl has unsound usages of `core::slice::from_raw_parts_mut`

Also known asRUSTSEC-2024-0424

Published

Dec 23, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀libafl

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 breaks the safety assumptions when using unsafe API slice::from_raw_parts_mut. The pointer passed to from_raw_parts_mut is misaligned by casting u8 to u16 raw pointer directly, which is unsound. The bug is patched by using align_offset, which could make sure the memory address is aligned to 2 bytes for u16.

This was patched in 0.11.2 in the commit.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libafl`	all versions	0.11.2`cargo update -p libafl --precise 0.11.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libafl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libafl to 0.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7qj-v3vp-4856 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f7qj-v3vp-4856 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f7qj-v3vp-4856. 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 breaks the safety assumptions when using unsafe API `slice::from_raw_parts_mut`. The pointer passed to `from_raw_parts_mut` is misaligned by casting `u8` to `u16` raw pointer directly, which is unsound. The bug is patched by using `align_offset`, which could make sure the memory address is aligned to 2 bytes for `u16`. This was patched in 0.11.2 in the [commit](https://github.com/AFLplusplus/LibAFL/pull/1530/commits/5a60cb31ef587d71d09d534bba39bd3973c4b35d).

O3 Security · Impact-Aware SCA

Is GHSA-f7qj-v3vp-4856 in your dependencies?

O3 Security finds GHSA-f7qj-v3vp-4856 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works