CVE-2022-26826: Windows DNS Server Remote Code Execution Vulnerability
Published Apr 12, 2022
·Updated
Windows DNS Server Remote Code Execution Vulnerability
Affected Software
38 affected componentsFixes available
Microsoft Windows Server=20H2
Microsoft Windows Server 2019
Microsoft Windows Server 2019
Microsoft Windows 11=21H2
Microsoft Windows 11=21H2
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows 10=20H2
Microsoft Windows 10=20H2
Microsoft Windows 10=20H2
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1607
Microsoft Windows 10=1607
Microsoft Windows 10=21H1
Microsoft Windows 10=21H1
Microsoft Windows 10=21H1
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=1909
Microsoft Windows 10=1909
Microsoft Windows 10=1909
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 10=1909
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows Server 2016
Microsoft Windows Server 2016=20h2
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Event History
Apr 12, 2022
CVE Published
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Apr 15, 2022
CVE Published
via MITRE·07:05 PM
Data Sourced
via MITRE·07:05 PM
DescriptionSeverity
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-26826?
CVE-2022-26826 is rated as critical due to the potential for remote code execution in affected systems.
2
How do I fix CVE-2022-26826?
To fix CVE-2022-26826, apply the latest security updates provided by Microsoft for your affected Windows version.
3
What versions of Windows are affected by CVE-2022-26826?
CVE-2022-26826 affects multiple versions of Windows including Windows Server 2022, 2019, 2016, and various editions of Windows 10 and 11.
4
What is the attack vector for CVE-2022-26826?
CVE-2022-26826 can be exploited remotely without authentication, making it particularly dangerous for unprotected systems.
5
Are there any workarounds for CVE-2022-26826?
While patching is the recommended approach, disabling DNS functions can serve as a temporary workaround for CVE-2022-26826.