LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24850: ML-DSA Signature Verification Accepts Signatures with Repeated Hint Indices

The ML-DSA crate is a Rust implementation of the Module-Lattice-Based Digital Signature Standard (ML-DSA). Starting in version 0.0.4 and prior to version 0.1.0-rc.4, the ML-DSA signature verification implementation in the RustCrypto `ml-dsa` crate incorrectly accepts signatures with repeated (duplicate) hint indices. According to the ML-DSA specification (FIPS 204 / RFC 9881), hint indices within each polynomial must be **strictly increasing**. The current implementation uses a non-strict monotonic check (`<=` instead of `<`), allowing duplicate indices. This is a regression bug. The original implementation was correct, but a commit in version 0.0.4 inadvertently changed the strict `<` comparison to `<=`, introducing the vulnerability. Version 0.1.0-rc.4 fixes the issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A Rust cryptography library for ML-DSA signature verification may accept some invalid signatures. This weakens integrity checks for systems using affected RustCrypto ml-dsa versions. The issue is rated medium because it affects signature validity, not confidentiality or availability, and public sources do not indicate active exploitation.

Executive priority

Treat as a targeted cryptographic integrity fix. Update affected Rust services during the next security maintenance cycle, faster for systems relying on ML-DSA verification for authentication, update signing, or high-value trust decisions.

Technical view

RustCrypto ml-dsa versions 0.0.4 through before 0.1.0-rc.4 use a non-strict check for ML-DSA hint indices, accepting duplicate indices. FIPS 204 and RFC 9881 require strictly increasing indices within each polynomial. The bug is tracked as CWE-347 and fixed in 0.1.0-rc.4.

Likely exposure

Exposure is limited to applications that use the RustCrypto ml-dsa crate for ML-DSA signature verification in affected versions. Risk is higher where verification results authorize software updates, identities, transactions, or other trust decisions.

Exploitation context

The CVSS vector is network-reachable with low complexity and no privileges or user interaction, but impact is limited to integrity. No CISA KEV listing or cited source in the provided bundle reports active exploitation.

Researcher notes

The vulnerability is a regression from changing a strict comparison to a non-strict one. Public references include the advisory, issue, pull request, commits, FIPS 204, RFC 9881, and Wycheproof ML-DSA verification vectors. Evidence supports a medium integrity issue, not broader compromise.

Mitigation direction

  • Upgrade RustCrypto ml-dsa to version 0.1.0-rc.4 or later.
  • Inventory Rust projects and dependency lockfiles for affected ml-dsa versions.
  • Review vendor advisory and repository updates before deploying cryptographic changes.
  • Prioritize systems where ML-DSA verification gates trust or authorization decisions.

Validation and detection

  • Confirm deployed dependency versions are not >=0.0.4 and <0.1.0-rc.4.
  • Review Cargo dependency trees for transitive use of RustCrypto ml-dsa.
  • Run standard ML-DSA verification conformance tests, including Wycheproof test vectors where applicable.
  • Verify the fixed strict hint-index validation is present after upgrade.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24850 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
12Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24850Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RustCryptosignatures>= 0.0.4, < 0.1.0-rc.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.