Merge branch 'master' into 681_remove_storage_read

.clusterfuzzlite/Dockerfile

@@ -1,7 +1,4 @@
 FROM gcr.io/oss-fuzz-base/base-builder-rust:v1
-RUN rustup install nightly-2024-09-24 && rustup default nightly-2024-09-24
-RUN rustup component add rust-src --toolchain nightly-2024-09-24
-ENV RUSTUP_TOOLCHAIN=nightly-2024-09-24
 COPY . $SRC/fuel-vm
 WORKDIR fuel-vm
 COPY .clusterfuzzlite/build.sh $SRC/

CHANGELOG.md

@@ -7,8 +7,11 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ## [Unreleased]
 
-### Changed
-- [#847](https://github.com/FuelLabs/fuel-vm/pull/847): LDC optimization avoids allocating extra memory when loading contract code onto the stack.
+### Changed 
+- [#847](https://github.com/FuelLabs/fuel-vm/pull/847): Remove `contract_read`, and change `load_contract_code`, `code_copy` and `code_root`  to explicitly load the contract code in a buffer. Also check for mismatches between contract size stored and actual size of contract in those functions.
+
+### Fixed
+- [860](https://github.com/FuelLabs/fuel-vm/pull/860): Fixed missing fuzzing coverage report in CI.
 
 ## [Version 0.58.2]
 

SECURITY.md

@@ -0,0 +1,31 @@
+# Fuel Security Policy
+
+Thank you for helping make the Fuel ecosystem safe for everyone. The Fuel team take security bugs very seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+
+## Reporting Security Issues
+
+If you believe you have found a security vulnerability in any Fuel-owned repository, please report it to us through coordinated disclosure.
+
+**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
+
+Instead, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/FuelLabs/fuel-vm/security/advisories/new) tab.
+
+The Fuel team will send a response indicating the next steps in handling your report. After the initial reply to your report, the team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
+
+Please include as much of the information listed below as you can to help us better understand and resolve the issue:
+
+* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
+* Full paths of source file(s) related to the manifestation of the issue
+* The location of the affected source code (tag/branch/commit or direct URL)
+* Any special configuration required to reproduce the issue
+* Step-by-step instructions to reproduce the issue
+* Proof-of-concept or exploit code (if possible)
+* Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+Report security bugs in third-party modules to the person or team maintaining the module.
+
+## Non-Security Issues
+
+If the issue is not security-related, please report it publicly by opening a [GitHub Issue](https://github.com/FuelLabs/fuel-vm/issues/new).