How broadly exploitable is this timing side-channel issue?

Exploitability depends on the attacker's ability to repeatedly exercise affected operations and measure their execution time with sufficient precision. On embedded systems like Cortex-M0/M0+/M1, this may be feasible when the attacker has physical access, shared hardware, or a tightly coupled external interface.

Does an attacker need direct code execution or authentication to exploit this?

Not necessarily. The attacker primarily needs a way to trigger the vulnerable code paths and observe timing differences. This could be over a protocol implemented on the MCU, a side-channel measurement setup, or a local interface, rather than full code execution or privileged access.

What is the safest general fix pattern for affected code?

The safest pattern is to use constant-time primitives that are explicitly validated for the target architecture—typically through dedicated intrinsics or assembly—and to verify that the compiled output remains branchless and data-independent for all supported toolchains and optimization levels.

Severity:

CRITICAL RISK

(9.8)

Timing Side-Channel in Conditional Move Intrinsics (CWE-208) on thumbv6m RustCrypto CMOV

CVE-2026-23519

Published:

Jan 15, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Timing Side-Channel / Side-Channel Vulnerability

CWE:

CWE-208;CWE-203

Impact:

Timing side-channel leakage of sensitive information

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Timing Side-Channel / Side-Channel Vulnerability

CWE:

CWE-208;CWE-203

Impact:

Timing side-channel leakage of sensitive information

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Timing Side-Channel in Conditional Move Intrinsics (CWE-208) on thumbv6m RustCrypto CMOV

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare