Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. fuel-vm
  4. ›
  5. GHSA-2pgj-5cv2-6xxw

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

October 8, 2025

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.

References

  • github.com/FuelLabs/fuel-vm
  • github.com/FuelLabs/fuel-vm/commit/9c97c2bf782626b35ba48e154f210f91c847a513
  • github.com/FuelLabs/fuel-vm/pull/941
  • github.com/FuelLabs/fuel-vm/security/advisories/GHSA-2pgj-5cv2-6xxw
  • github.com/advisories/GHSA-2pgj-5cv2-6xxw

Code Behaviors & Features

Detect and mitigate GHSA-2pgj-5cv2-6xxw with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.59.3, all versions starting from 0.60.0 before 0.60.1

Fixed versions

  • 0.59.3
  • 0.60.1

Solution

Upgrade to versions 0.59.3, 0.60.1 or above.

Weakness

  • CWE-416: Use After Free

Source file

cargo/fuel-vm/GHSA-2pgj-5cv2-6xxw.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sun, 09 Nov 2025 12:18:55 +0000.