Skip to main content

Cmov CVE-2026-23519

CRITICAL
Observable Timing Discrepancy (CWE-208)
2026-01-15 security-advisories@github.com GHSA-2gqc-6j2q-83qp
9.8
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Target ARM Cortex M0/M0+/M1 device
  2. Exploit
    Deploy RustCrypto CMOV <0.4.4
  3. Execution
    Exploit timing side-channel in cmovnz
  4. Impact
    Extract cryptographic secrets via power analysis

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V6 - Authentication Timing attack prevention
Exploitation Conditions

RustCrypto CMOV library version <0.4.4 compiled for thumbv6m-none-eabi (Cortex M0, M0+, M1 ARM processors). Attacker requires physical or side-channel access to measure timing/power consumption of the target device during cryptographic operations.

Impact

CVSS 9.8 (Critical). Network vector (timing observable over network). PoC available. Patch available. Affects embedded cryptographic implementations on popular IoT processors. EPSS 0.03%.

Exploit ScenarioDerived

An attacker measures the timing of cryptographic operations on an IoT device using a Cortex-M0, using statistical analysis to recover secret keys through the timing side channel.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

RustCrypto CMOV before 0.4.4 emits non-constant-time assembly on ARM Cortex-M0/M0+/M1 targets. Cryptographic operations that rely on constant-time guarantees are broken on these embedded platforms. PoC available, patch available.

Earlier versions of this analysis (1)
v1 Mar 12, 2026 - 21:54 CVSS 9.8

RustCrypto CMOV breaks constant-time guarantees on ARM Cortex-M0 targets, enabling timing side-channel attacks.

RemediationAI

Update to CMOV 0.4.4.

Affected Packages

cargo cmov fix: 0.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in cargo

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The cmovnz portable implementation compiles to branching (non-constant-time) assembly on thumbv6m-none-eabi (CWE-208). Cryptographic code using CMOV for secret-dependent operations leaks timing information.

Know when Cmov gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
PoC Detected
Jan 23, 2026 - 18:59 vuln.today
Public exploit code
Patch released
Jan 23, 2026 - 18:59 nvd
Patch available
CVE Published
Jan 15, 2026 - 20:16 nvd
CRITICAL 9.8

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

Organizations using constant-time and not be rewritten as branches by the compiler. face critical risk from CVE-2026-23519 rated CVSS 9.8. Successful exploitation could critically impact the confidentiality, integrity, and availability of affected systems. Proof-of-concept code is publicly available, increasing the risk of exploitation. A patch is available and should be applied immediately given the critical severity.

Business Impact: Severe
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

69
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:rustcrypto:cmov:*:*:*:*:*:rust:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy