CVE-2026-50303
Microsoft Windows 10 21H2 ≤ 10.0.19044.7548
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2026-50303 is a medium-severity Use of a Cryptographic Primitive with a Risky Implementation (CWE-1240) vulnerability in Microsoft Windows 10 21H2. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Weaken Encryption (T1600); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-43846
Vulnerability Data
Use of a cryptographic primitive with a risky implementation in Windows Key Guard allows an authorized attacker to bypass a security feature locally.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 12 hardening rules · 3 OS baselines
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires specific, validated cryptographic primitives, reducing use of risky or improperly implemented primitives.
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.
Secure SDLC practices directly require use of approved, proven cryptographic implementations and forbid risky custom ones.
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.
Mandates approved cryptographic controls, directly preventing use of risky or non-compliant implementations.
Security testing can detect use of weak or non-compliant cryptographic primitives before deployment.
Secure SDLC requires vetted crypto libraries and standards, reducing risky custom implementations.
Application security requirements can specify approved cryptographic standards and disallow risky primitives.
Secure architecture principles include selection of proven cryptographic components and avoidance of custom risky implementations.
Secure coding standards prohibit non-standard or disallowed cryptographic algorithms.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-1240
- V-248534 OL 8 must employ FIPS 140-2 approved cryptographic hashing algorithms for all stored passwords. prevents CWE-1240
Oracle Linux 9 (1 rule)
- V-271628 OL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords. prevents CWE-1240
RHEL 8 (2 rules)
- V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-1240
- V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. prevents CWE-1240