From b7838f048d31c7b62a064036a75e1d6cd7e95077 Mon Sep 17 00:00:00 2001 From: Samuel Ojetunde Date: Mon, 26 Oct 2026 12:52:05 +0100 Subject: [PATCH] chore(deny): document RUSTSEC-2026-0387 as test-host only crypto-bigint 0.5 (timing variability in constant-time operations, fixed only in 0.7.6) comes in through soroban-env-host's elliptic-curve 0.13, the native test host. That chain requires 0.5, which has no fixed release, and soroban-sdk 29 still uses it. cargo tree -e normal --target wasm32v1-none shows the deployed contract does not contain it. Ignore it with the reason and the condition for removing it, like the other test-host advisories. --- deny.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/deny.toml b/deny.toml index b372340..9e95aac 100644 --- a/deny.toml +++ b/deny.toml @@ -11,6 +11,12 @@ ignore = [ # through soroban-env-host, the native test host; the deployed WASM does not # contain it. { id = "RUSTSEC-2024-0436", reason = "build-time macro of the test host, absent from the contract" }, + # `crypto-bigint` 0.5 has timing variability in constant-time operations, + # fixed only in 0.7.6. It is reached only through soroban-env-host's + # elliptic-curve 0.13, the native test host; `cargo tree -e normal --target + # wasm32v1-none -i crypto-bigint` shows the deployed WASM does not contain + # it, and soroban-sdk 29 still uses 0.5. Remove once soroban moves to 0.7. + { id = "RUSTSEC-2026-0387", reason = "test host only (elliptic-curve 0.13), absent from the contract; no 0.5.x fix exists" }, ] [licenses]