CyberSecBulletin
CVE-2025-58720NVD status: Analyzed

Windows 10 Version 1809: Use of a Cryptographic Primitive with a Risky Implementation

Published Updated By the CyberSecBulletin desk

CVE-2025-58720 is a high-severity use of a cryptographic primitive with a risky implementation vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.17763.7919 as the first without the flaw, so updating Windows 10 Version 1809 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1809 to 10.0.17763.7919 or a later version.
  2. Update Windows 10 Version 21H2 to 10.0.19044.6456 or a later version.
  3. Update Windows 10 Version 22H2 to 10.0.19045.6456 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.791910.0.17763.7919
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.645610.0.19044.6456
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.645610.0.19045.6456
MicrosoftWindows 11 version 22H210.0.22621.0 up to, but not including, 10.0.22621.606010.0.22621.6060
MicrosoftWindows 11 version 22H310.0.22631.0 up to, but not including, 10.0.22631.606010.0.22631.6060
MicrosoftWindows 11 Version 23H210.0.22631.0 up to, but not including, 10.0.22631.606010.0.22631.6060
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.689910.0.26100.6899
MicrosoftWindows 11 Version 25H210.0.26200.0 up to, but not including, 10.0.26200.689910.0.26200.6899
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.791910.0.17763.7919
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.791910.0.17763.7919
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.429410.0.20348.4294
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0 up to, but not including, 10.0.25398.191310.0.25398.1913
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.689910.0.26100.6899
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.689910.0.26100.6899
MicrosoftWindows 10 1809before 10.0.17763.791910.0.17763.7919
MicrosoftWindows 10 21h2before 10.0.19044.645610.0.19044.6456
MicrosoftWindows 10 22h2before 10.0.19045.645610.0.19045.6456
MicrosoftWindows 11 22h2before 10.0.22621.606010.0.22621.6060
MicrosoftWindows 11 23h2before 10.0.22631.606010.0.22631.6060
MicrosoftWindows 11 24h2before 10.0.26100.689910.0.26100.6899
MicrosoftWindows 11 25h2before 10.0.26200.689910.0.26200.6899
MicrosoftWindows Server 2022 23h2before 10.0.25398.191310.0.25398.1913

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Use of a cryptographic primitive with a risky implementation in Windows Cryptographic Services allows an authorized attacker to disclose information locally.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of a Cryptographic Primitive with a Risky Implementation

To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation.

How developers prevent this class of flaw

  • Require compliance with the strongest-available recommendations from trusted parties, and require that compliance must be kept up-to-date, since recommendations evolve over time. For example, US government systems require FIPS 140-3 certification, which supersedes FIPS 140-2.
  • Ensure that the architecture/design uses the strongest-available primitives and algorithms from trusted parties. For example, US government systems require FIPS 140-3 certification, which supersedes FIPS 140-2.
  • Do not develop custom or private cryptographic algorithms. They will likely be exposed to attacks that are well-understood by cryptographers. As with all cryptographic mechanisms, the source code should be available for analysis. If the algorithm may be compromised when attackers find out how it works, then it is especially weak.

More Use of a Cryptographic Primitive with a Risky Implementation vulnerabilities (CWE-1240)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use of a Cryptographic Primitive with a Risky Implementation vulnerabilities

Spotted an error? Tell us.