{"answers":{"affected":"1 open source package ship an affected version, including crypto-bigint.","exploited":"There is no known exploitation of RUSTSEC-2026-0387 in the wild and no public exploit code.","fix":"Upgrade crypto-bigint to 0.7.6 or later.","what":"RUSTSEC-2026-0387 is a vulnerability in crypto-bigint, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0387 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0387 is a vulnerability in crypto-bigint, published on 23 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0387 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crypto-bigint (crates.io): affected from 0.0.0-0; fixed in 0.7.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0387/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0387/index.md)","id":"RUSTSEC-2026-0387","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0387/index.md","name":"RUSTSEC-2026-0387","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Summary\n\nSeveral operations intended to be constant-time could execute secret-dependent\nbranches, depending on the compiler and target CPU. These include subtraction,\nzero counting, division, and Montgomery multiplication.\n\nAdditionally, `UintRef` equality could terminate at the first unequal limb,\nand `BoxedMontyForm::invert` branched on whether an inverse exists.\n\n## Impact\n\nApplications using affected operations on secret integers may leak information\nthrough timing or microarchitectural side channels. This includes information\nabout intermediate arithmetic values, matching limbs, and invertibility.\n\nSuch leakage could potentially enable recovery of cryptographic secrets.\nPractical exploitability depends on the downstream algorithm, compiler, target\nCPU, and an attacker's ability to observe the side channel.\n\n## Resolution\n\nUpgrade to v0.7.6, which removes the identified branches, updates `ctutils` to\ninclude its constant-time fixes, and adds BINSEC-based regression checks using\n`cargo checkct` for arithmetic on multiple targets.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Multiple timing variability issues in operations intended to be constant-time","id":"RUSTSEC-2026-0387","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.6"],"introduced":["0.0.0-0"],"last_affected":[],"package":"crypto-bigint","purl":"pkg:cargo/crypto-bigint","source":"RUSTSEC-2026-0387"}],"products":null,"published":"2026-10-23","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0387/"}