Skip to content
Infrastructure

CVE-2026-49169

8.0
High
EPSS 0.75%Patch availableJul 15, 2026

Use-after-free in DNS Server enabling authenticated remote code execution.

common questions

Is CVE-2026-49169 being exploited?

Not confirmed. CVE-2026-49169 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.75% probability of exploitation in the next 30 days.

How severe is CVE-2026-49169?

CVE-2026-49169 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49169?

Yes. A fix has been recorded for CVE-2026-49169. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49169 affect?

CVE-2026-49169 affects DNS Server (vendor unspecified), DNS server software/daemons. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49169?

Restrict DNS admin access, apply vendor patch when available, add network ACLs and monitor logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
DNS Server (vendor unspecified)DNS server software/daemons
impact

Authenticated attacker can trigger a DNS server use-after-free to execute arbitrary code remotely, risking full system compromise.

action required

Immediate action required

affected versions
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33158
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33158

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free