Skip to content
VulniPulse
Sign in
Advisory severityMedium6.5Vendor: HighMicrosoft Server

Medium [CVE-2026-97839] Role: DNS Server Information Disclosure Vulnerability

This medium-severity Microsoft Server advisory covers CVE-2026-97839 affecting Windows Server 2012 R2, Windows Server 2016, Windows Server 2019.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-97839 Source published Source updated

VulniPulse record published Record updated

CVE-2026-97839
Affected products & platforms
Microsoft ServerWindows Server
Open source advisory

Summary

Role: DNS Server Information Disclosure Vulnerability

Affected products named by the advisory: Windows Server 2012; Windows Server 2012 R2; Windows Server 2016; Windows Server 2019; and 2 more.

Affected products named by the advisory: Windows Server 2022; Windows Server 2025.

Is CVE-2026-97839 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-97839 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-97839?

Upgrade to a fixed release named by Microsoft:

  • KB5126835 (build 6.2.9200.26434)
  • KB5126836 (build 6.3.9600.23470)
  • KB5126868 (build 10.0.14393.9612)
  • KB5126651 (build 10.0.17763.9376)
  • KB5126657 (build 10.0.19045.7807)
  • KB5126655 (build 10.0.20348.5761)
  • KB5126653 (build 10.0.22631.7652)
  • KB5127648 (build 10.0.26300.9711)

Confirm against the vendor advisory before you patch.

Affected versions
  • Windows 10 Version 1607 10.0.14393.0 before 10.0.14393.9612
  • Windows 10 Version 1809 10.0.17763.0 before 10.0.17763.9376
  • Windows 10 Version 21H2 10.0.19044.0 before 10.0.19044.7807
  • Windows 10 Version 22H2 10.0.19045.0 before 10.0.19044.7807
  • Windows 11 version 23H2 10.0.22631.0 before 10.0.22631.7652
  • Windows 11 Version 23H2 10.0.22631.0 before 10.0.22631.7652
  • Windows 11 Version 24H2 10.0.26100.0 before 10.0.26100.9711
  • Windows 11 Version 25H2 10.0.26200.0 before 10.0.26200.9711
  • Windows 11 version 26H1 10.0.28000.0 before 10.0.28000.3231
  • Windows 11 Version 26H2 10.0.26300.0 before 10.0.26300.9711
  • Windows Server 2012 6.2.9200.0 before 6.2.9200.26434
  • Windows Server 2012 (Server Core installation) 6.2.9200.0 before 6.2.9200.26434

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions
  • KB5126835 (build 6.2.9200.26434)
  • KB5126836 (build 6.3.9600.23470)
  • KB5126868 (build 10.0.14393.9612)
  • KB5126651 (build 10.0.17763.9376)
  • KB5126657 (build 10.0.19045.7807)
  • KB5126655 (build 10.0.20348.5761)
  • KB5126653 (build 10.0.22631.7652)
  • KB5127648 (build 10.0.26300.9711)

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Install the applicable security update for your platform: KB5126835, KB5126836, KB5126868, KB5126651, KB5126657, KB5126655 (see the Microsoft Update Catalog).

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Get an email when Windows Server publishes the next one.

See Windows Server's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Windows Server

More Microsoft Server advisories

All Microsoft Server advisories

iPhone and Android apps · New on the App Store

Monitor future Microsoft Server CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.