LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23519: RustCrypto cmov: thumbv6m-none-eabi compiler emits non-constant time assembly when using cmovnz

RustCrypto CMOV provides conditional move CPU intrinsics which are guaranteed on major platforms to execute in constant-time and not be rewritten as branches by the compiler. Prior to 0.4.4, the thumbv6m-none-eabi (Cortex M0, M0+ and M1) compiler emits non-constant time assembly when using cmovnz (portable version). This vulnerability is fixed in 0.4.4.

HighCVSS 8.9Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-23519 affects RustCrypto’s cmov utility before 0.4.4 when compiled for thumbv6m-none-eabi Cortex-M0/M0+/M1 targets. A compiler output issue can make a supposedly constant-time operation non-constant-time, potentially leaking secrets through timing behavior. This is mainly urgent for embedded products using RustCrypto cryptography on those microcontrollers.

Executive priority

Treat as high priority for affected embedded cryptographic products, especially devices handling keys or sensitive data. For organizations not using RustCrypto cmov on thumbv6m-none-eabi microcontrollers, urgency is lower. Focus first on dependency inventory and firmware release planning.

Technical view

RustCrypto cmov promises conditional move intrinsics that remain constant-time. Before version 0.4.4, the portable cmovnz path on thumbv6m-none-eabi may compile into non-constant-time assembly. The assigned weakness is CWE-208, Observable Timing Discrepancy. CVSS v4.0 is 8.9, with high confidentiality impact and high attack complexity.

Likely exposure

Exposure is likely limited to projects using RustCrypto utils/cmov versions before 0.4.4 and building for thumbv6m-none-eabi, specifically Cortex-M0, M0+, or M1. General server, desktop, or unrelated embedded targets are not identified as affected in the provided sources.

Exploitation context

The issue is a timing side channel, not memory corruption or remote code execution. The CVSS vector lists network attack vector but high attack complexity. The source bundle does not report active exploitation, and KEV is false. Practical risk depends on reachable cryptographic operations and attacker ability to observe timing differences.

Researcher notes

The public record identifies the vulnerable condition and fix version, but does not include exploitation evidence. Review the linked commit and advisory to understand the code change. Avoid assuming broader platform impact beyond thumbv6m-none-eabi unless vendor sources expand the scope.

Mitigation direction

  • Upgrade RustCrypto utils/cmov to version 0.4.4 or later.
  • Prioritize embedded firmware builds targeting thumbv6m-none-eabi.
  • Check RustCrypto’s advisory for any updated guidance.
  • Rebuild and redeploy affected firmware after dependency update.

Validation and detection

  • Inventory Rust projects using RustCrypto utils or cmov.
  • Check dependency lockfiles for cmov versions below 0.4.4.
  • Identify builds targeting thumbv6m-none-eabi Cortex-M0, M0+, or M1.
  • Confirm rebuilt firmware uses cmov 0.4.4 or later.
Prepared
Confidence
high
Sources
4

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-208: 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-23519 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
High
CVSS
8.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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
3Source 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
8.9CVSS 4.0HighCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.9High
CVSS 4.0 vector shape for CVE-2026-23519Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RustCryptoutils< 0.4.4Listed
Weakness

CWE details

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

CWE-208 · source CWE mapping

Observable Timing Discrepancy

Observable Timing Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.