How severe is GHSA-2pgj-5cv2-6xxw?

No CVSS score has been assigned to GHSA-2pgj-5cv2-6xxw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2pgj-5cv2-6xxw?

GHSA-2pgj-5cv2-6xxw affects the following packages: fuel-vm (crates.io), fuel-vm (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2pgj-5cv2-6xxw?

Update fuel-vm to 0.59.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pgj-5cv2-6xxw is resolved across your whole dependency graph.

How do I detect GHSA-2pgj-5cv2-6xxw in my crates.io dependencies?

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

How do I mitigate GHSA-2pgj-5cv2-6xxw if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-2pgj-5cv2-6xxw actively exploited in the wild?

No public exploit code has been indexed for GHSA-2pgj-5cv2-6xxw 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-2pgj-5cv2-6xxw published, and has it been updated?

GHSA-2pgj-5cv2-6xxw was published on October 8, 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

FuelVM is vulnerable to heap memory allocation re-use bugGHSA-2pgj-5cv2-6xxw

Fix: FuelLabs/fuel-vm#941

GHSA-2pgj-5cv2-6xxw is a security vulnerability in fuel-vm. A fix is available for fuel-vm — see the affected versions and patch details below.

Published

Oct 8, 2025

Updated

Oct 8, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

🦀fuel-vm🦀fuel-vm

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

Impact

A memory safety vulnerability was present in the Fuel Virtual Machine (FuelVM), where memory reads could bypass expected access controls. Specifically, when a smart contract performed a mload (or other opcodes which access memory) on memory that had been deallocated using ret, it was still able to access the old memory contents. This occurred because the memory region was not zeroed out or otherwise marked as invalid. As a result, smart contracts could potentially read sensitive data left over from other contracts if the same memory was reallocated, violating isolation guarantees between contracts and enabling unintended data leakage.

All users running affected versions of FuelVM that relied on strict memory isolation between smart contracts were impacted.

Patches

The vulnerability was patched by modifying the FuelVM to ensure that memory deallocated with ret was zeroed out or made inaccessible. The fix was included in FuelVM version v0.60.1 and back-ported to v0.59.3. This patch was released to the Fuel network on Friday, April 18th, 2025.

Workarounds

There were no reliable workarounds that fully mitigated the vulnerability. While developers could manually zero out sensitive memory regions before returning from a function, this approach was error-prone and could not be enforced at the VM level. Upgrading to a patched version remained the recommended course of action.

References

Fix implemented in the FuelVM GitHub repository (https://github.com/FuelLabs/fuel-vm/pull/941)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`fuel-vm`	all versions	0.59.3`cargo update -p fuel-vm --precise 0.59.3`
🦀crates.io	`fuel-vm`	≥ 0.60.0&&< 0.60.1	0.60.1`cargo update -p fuel-vm --precise 0.60.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuel-vm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fuel-vm to 0.59.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pgj-5cv2-6xxw is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact A memory safety vulnerability was present in the Fuel Virtual Machine (FuelVM), where memory reads could bypass expected access controls. Specifically, when a smart contract performed a `mload` (or other opcodes which access memory) on memory that had been deallocated using `ret`, it was still able to access the old memory contents. This occurred because the memory region was not zeroed out or otherwise marked as invalid. As a result, smart contracts could potentially read sensitive data left over from other contracts if the same memory was reallocated, violating isolation guarante

O3 Security · Impact-Aware SCA

Is GHSA-2pgj-5cv2-6xxw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works