NVD / CVE Program· CNA microsoft

CVE-2024-26223: Windows DNS Server Remote Code Execution Vulnerability

MediumCVSS 6.6 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.5% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Windows Server 2016 10.0.14393.6897; Windows Server 2016 (Server Core installation) 10.0.14393.6897; Windows Server 2019 10.0.17763.5696.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Windows Server 2016 10.0.14393.6897; Windows Server 2016 (Server Core installation) 10.0.14393.6897; Windows Server 2019 10.0.17763.5696 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

BDU:2024-03513

Published: Apr 9, 2024
Updated: Jun 17, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.6
CNA · microsoft: 7.2; 0.6 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
microsoft	windows server 2016	cpe:2.3:o:microsoft:windows_server_2016
microsoft	windows server 2019	cpe:2.3:o:microsoft:windows_server_2019
microsoft	windows server 2022	cpe:2.3:o:microsoft:windows_server_2022
microsoft	windows server 2022 23h2	cpe:2.3:o:microsoft:windows_server_2022_23h2

Using windows server 2016? Add it to your stack and be the first to know about CVEs like this one. (Windows Server, Active Directory)

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

Microsoft Windows Server 2016
- 10.0.14393.0 and later · before 10.0.14393.6897affected
Microsoft Windows Server 2016 (Server Core installation)
- 10.0.14393.0 and later · before 10.0.14393.6897affected
Microsoft Windows Server 2019
- 10.0.17763.0 and later · before 10.0.17763.5696affected
Microsoft Windows Server 2019 (Server Core installation)
- 10.0.17763.0 and later · before 10.0.17763.5696affected
Microsoft Windows Server 2022
- 10.0.20348.0 and later · before 10.0.20348.2402affected
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
- 10.0.25398.0 and later · before 10.0.25398.830affected

Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microsoft windows server 2016before 10.0.14393.6897
microsoft windows server 2019before 10.0.17763.5696
microsoft windows server 2022before 10.0.20348.2402
microsoft windows server 2022 23h2before 10.0.25398.830

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

CVE-2024-38076Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
40Plan
CVE-2021-34458Windows Kernel Remote Code Execution Vulnerability
40Plan
CVE-2026-88243Windows DHCP Server Remote Code Execution Vulnerability
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-26221Apr 9, 2024 · Windows DNS Server Remote Code Execution Vulnerability
27Monitor
← EarlierCVE-2024-26222Apr 9, 2024 · Windows DNS Server Remote Code Execution Vulnerability
27Monitor
Later →CVE-2024-26224Apr 9, 2024 · Windows DNS Server Remote Code Execution Vulnerability
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Windows Server 2016	10.0.14393.6897 · KB5036899	Microsoft (MSRC)
Windows Server 2016 (Server Core installation)	10.0.14393.6897 · KB5036899	Microsoft (MSRC)
Windows Server 2019	10.0.17763.5696 · KB5036896	Microsoft (MSRC)
Windows Server 2019 (Server Core installation)	10.0.17763.5696 · KB5036896	Microsoft (MSRC)
Windows Server 2022	10.0.20348.2402 · KB5036909	Microsoft (MSRC)
Windows Server 2022 (Server Core installation)	10.0.20348.2402 · KB5036909	Microsoft (MSRC)
Windows Server 2022, 23H2 Edition (Server Core installation)	10.0.25398.830 · KB5036910	Microsoft (MSRC)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-49116246 days apartWindows Remote Desktop Services Remote Code Execution Vulnerability
35Monitor
CVE-2024-49106246 days apartWindows Remote Desktop Services Remote Code Execution Vulnerability
32Monitor
CVE-2024-49108246 days apartWindows Remote Desktop Services Remote Code Execution Vulnerability
32Monitor
CVE-2024-49115246 days apartWindows Remote Desktop Services Remote Code Execution Vulnerability
32Monitor
CVE-2024-38138126 days apartWindows Deployment Services Remote Code Execution Vulnerability
30Monitor
CVE-2024-262220 days apartWindows DNS Server Remote Code Execution Vulnerability
27Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0282 · Apr 15, 2024(Windows Güvenlik Bildirimi)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: High
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Nov 12, 2026, 3:42 AM UTC

For records you follow, these changes also arrive as notifications. →

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26223

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records