Advisory record · GHSA-r7wm-4vf2-h44w

LLVM introduces timing-vulnerable optimizations into ML-KEM and ML-DSA operations intended to be constant-time

No CVSS score

Published by the GitHub Advisory Database at 30 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
orioncrates.io>=0.0.0-0, <0.17.16 || >=0.18.0-0, <0.18.10.17.16, 0.18.1
Identifiers
GHSA-r7wm-4vf2-h44w · RUSTSEC-2026-0426
Published
30 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The orion crate versions before 0.17.16 and from 0.18.0 up to (not including) 0.18.1 are affected. On certain targets, such as i586 and s390x Linux and some x86_64 ML-DSA builds, LLVM can compile a helper function used in ML-KEM and ML-DSA arithmetic into a conditional jump depending on secret data. An attacker with the ability to observe timing could potentially recover cryptographic secrets, and exploitability depends on the compiler, target CPU, and attacker proximity. Upgrade to orion 0.17.16 or 0.18.1.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.