RUSTSEC-2026-0387 json
Multiple timing variability issues in operations intended to be constant-time
published 19d ago modified 19d ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
## Summary
Several operations intended to be constant-time could execute secret-dependent branches, depending on the compiler and target CPU. These include subtraction, zero counting, division, and Montgomery multiplication.
Additionally, `UintRef` equality could terminate at the first unequal limb, and `BoxedMontyForm::invert` branched on whether an inverse exists.
## Impact
Applications using affected operations on secret integers may leak information through timing or microarchitectural side channels. This includes information about intermediate arithmetic values, matching limbs, and invertibility.
Such leakage could potentially enable recovery of cryptographic secrets. Practical exploitability depends on the downstream algorithm, compiler, target CPU, and an attacker's ability to observe the side channel.
## Resolution
Upgrade to v0.7.6, which removes the identified branches, updates `ctutils` to include its constant-time fixes, and adds BINSEC-based regression checks using `cargo checkct` for arithmetic on multiple targets.
Patch / fix
Is RUSTSEC-2026-0387 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | crypto-bigint | >=0.0.0-0, <0.7.6 |
0.7.6 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.