Cyber Resilience

CVE-2026-50185

Published
17 July 2026
Modified
23 July 2026
CVSS Score v4 2.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0011 2th percentile
Risk Priority 19 floored blend · peak EPSS

Summary

CVE-2026-50185 is a low-severity Reliance on Undefined, Unspecified, or Implementation-Defined Behavior (CWE-758) vulnerability. Its CVSS base score is 2.0 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

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. From 0.1.1 until 0.5.4, the aarch64 implementations of Cmov and CmovEq in cmov/src/backends/aarch64.rs assume…

more

high bits are zero-extended when loading values smaller than a register, so set high bits such as [8..] in a Cmov selector or [16..] of self or other in the u16 and i16 CmovEq implementations can cause left.cmovz(&right, condition) to produce incorrect output. This issue is fixed in version 0.5.4.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-30624Shared CWE-758
CVE-2026-34549Shared CWE-758
CVE-2026-4705Shared CWE-758
CVE-2024-4774Shared CWE-758
CVE-2026-34537Shared CWE-758
CVE-2026-34547Shared CWE-758
CVE-2025-54811Shared CWE-758
CVE-2026-16441Shared CWE-758
CVE-2026-4718Shared CWE-758
CVE-2025-55160Shared CWE-758

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover reliance on undefined behavior through cross-platform or stress testing.

Mandating a documented development process and coding standards directly discourages dependence on unspecified behavior.

Engineering principles can require use of only well-defined language and API behaviors during development.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prohibit use of undefined or implementation-defined behavior in code.

PR.PS-01 partial match
prevents

Consistent hardened configurations reduce the chance of relying on unspecified implementation details.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect some instances of undefined behavior but does not prevent the root weakness.

prevents

Secure development life cycle requires defined, portable coding practices that reduce reliance on undefined behavior.

degrades

Secure system architecture and engineering principles mandate use of well-specified interfaces and avoid undefined constructs.

prevents

Secure coding explicitly prohibits constructs whose behavior is undefined, unspecified or implementation-defined.

References