CyberSecBulletin
CVE-2026-83645NVD status: Analyzed

Windows 10 Version 1607: Allocation of Resources Without Limits or Throttling

CVE-2026-83645 is a high-severity allocation of resources without limits or throttling vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.0.14393.9612 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.22% chance of exploitation within 30 days, higher than 69% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1607 to 10.0.14393.9612 or a later version.
  2. Update Windows 10 Version 1809 to 10.0.17763.9376 or a later version.
  3. Update Windows Server 2012 to 6.2.9200.26434 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.961210.0.14393.9612
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.937610.0.17763.9376
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.264346.2.9200.26434
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.264346.2.9200.26434
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.234706.3.9600.23470
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.234706.3.9600.23470
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.961210.0.14393.9612
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.961210.0.14393.9612
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.937610.0.17763.9376
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.937610.0.17763.9376
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.576110.0.20348.5761
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.3365010.0.26100.33650
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.3365010.0.26100.33650
MicrosoftWindows 10 1607before 10.0.14393.961210.0.14393.9612
MicrosoftWindows 10 1809before 10.0.17763.937610.0.17763.9376

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
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

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

Official description

Allocation of resources without limits or throttling in Active Directory Federation Services (AD FS) allows an unauthorized attacker to deny service over a network.

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

The underlying weakness: Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How developers prevent this class of flaw

  • Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
  • Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)

Timeline

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

References

Recent Allocation of Resources Without Limits or Throttling vulnerabilities

Spotted an error? Tell us.