Skip to content

Document RUSTSEC-2026-0387 (crypto-bigint) as test-host only - #11

Merged
samjay8 merged 1 commit into
mainfrom
fix/security-advisories
Oct 26, 2026
Merged

samjay8 merged 1 commit into
mainfrom
fix/security-advisories

Conversation

@samjay8

@samjay8 samjay8 commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

cargo deny now fails on RUSTSEC-2026-0387: crypto-bigint before 0.7.6 has timing variability in operations meant to be constant-time.

It can't be fixed by an update yet. crypto-bigint 0.5.5 comes in only through elliptic-curve 0.13 in soroban-env-host, the native Soroban host that runs the tests. That chain requires the 0.5 series, which has no fixed release, and soroban-sdk 29 still uses it.

It isn't in the deployed contract:

$ cargo tree -e normal --target wasm32v1-none -i crypto-bigint
warning: nothing to print.

So this adds the advisory to deny.toml's ignore list, with the reason and the condition for removing it (soroban moving to crypto-bigint 0.7). That's the same treatment as the test-host-only advisories already listed there.

Checked

cargo deny check: advisories, bans, licenses and sources all ok.

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.
@samjay8
samjay8 merged commit 6f8377d into main Oct 26, 2026
4 checks passed
@samjay8
samjay8 deleted the fix/security-advisories branch October 26, 2026 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant