Windows info-disclosure 0-day bug gets a fix as CISA sounds alarm
(2026/01/14)
- Reference: 1768350960
- News link: https://www.theregister.co.uk/2026/01/14/patch_tuesday_january_2026/
- Source link:
Microsoft and Uncle Sam have warned that a Windows bug disclosed today is already under attack.
The flaw, tracked as [1]CVE-2026-20805 and discovered by Microsoft's own threat intel team, allows an authorized attacker to leak a memory address from a remote ALPC port.
"Presumably, threat actors would then use the address in the next stage of their exploit chain – probably gaining arbitrary code execution," according to Trend Micro's Zero Day Initiative Head of Threat Awareness Dustin Childs' [2]analysis .
[3]
It's a medium-severity flaw, earning a 5.5 CVSS rating.
[4]
[5]
Shortly after Redmond pushed a patch, the US Cybersecurity and Infrastructure Security Agency [6]added CVE-2026-20805 to its [7]Known Exploited Vulnerabilities catalog , a step that means federal agencies must implement the fix by February 3. "This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise," the feds warned.
While we don't know who is abusing this hole, nor how widespread the exploitation is. Microsoft declined to answer our questions on the matter, so we'd suggest putting this patch at the top of the list.
[8]
"Vulnerabilities of this nature are commonly used to undermine Address Space Layout Randomization (ASLR), a core operating system security control designed to protect against buffer overflows and other memory-manipulation exploits," Kev Breen, senior director of cyber threat research at Immersive, told The Register .
"By revealing where code resides in memory, this vulnerability can be chained with a separate code execution flaw, transforming a complex and unreliable exploit into a practical and repeatable attack," he added, while also dinging Redmond for not disclosing which other components may be involved in such an exploit chain.
That omission, Breen said, "significantly" limits network defenders' "ability to proactively threat-hunt for related activity. As a result, rapid patching currently remains the only effective mitigation."
Two publicly known bugs
CVE-2026-20805 looks to be Microsoft's first zero-day bug of 2026, appearing on the first Patch Tuesday of the new year – and the patch dump is a whopper, with [9]112 Microsoft CVEs disclosed .
Of these, Microsoft lists two others as publicly known at the time of the release.
[10]
One of these, [11]CVE-2026-21265 , is a secure boot certificate expiration security feature bypass vulnerability, with a 6.4 CVSS rating. It's listed as publicly known because Microsoft [12]published this certificate expiration notice back in June 2025.
Some of the original certificates issued in 2011 are expiring soon, and operators of devices that use the soon-to-expire certificates need to update them – or lose the operating system's Secure Boot protections and security updates. As Childs noted, "while unlikely to be exploited, this bug could cause quite a bit of headaches for administrators."
[13]Frightful Patch Tuesday gives admins a scare with 175+ Microsoft CVEs, 3 under attack
[14]Patch Cisco ISE bug now before attackers abuse proof-of-concept exploit
[15]Popular Python libraries used in Hugging Face models subject to poisoned metadata attack
[16]CISA flags actively exploited Office relic alongside fresh HPE flaw
The other publicly known vulnerability, [17]CVE-2023-31096 , is a 7.8-rated elevation of privilege flaw in third-party Agere Modem drivers that ship with supported Windows versions. It's a non-Microsoft CVE that has to do with a flaw first documented in 2023 ( [18]CVE-2023-31096 ) and issued by MITRE.
During [19]October's patch-a-thon , Microsoft warned that this Agere Modem driver security hole had been made public, but not yet exploited, and said it would be removed in a future update. The future is now, and the drivers have been removed as of the January update.
A couple of other interesting bugs that Childs points out are these two, [20]CVE-2026-20952 (CVSS 7.7) and [21]CVE-2026-20953 (CVSS 7.4), both use-after-free Office flaws that can allow an unauthorized attacker to execute code locally.
"Another month with Preview Pane exploit vectors in an Office bug," Childs wrote. "While we are still unaware of any exploitation of these bugs, they keep adding up. It's only a matter of time until threat actors find a way to use these types of bugs in their exploits." ®
Get our [22]Tech Resources
[1] https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-20805
[2] https://www.zerodayinitiative.com/blog/2026/1/13/the-january-2026-security-update-review
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://www.cisa.gov/news-events/alerts/2026/01/13/cisa-adds-one-known-exploited-vulnerability-catalog
[7] https://www.cisa.gov/known-exploited-vulnerabilities-catalog
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://msrc.microsoft.com/update-guide/releaseNote/2026-Jan
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2026-21265
[12] https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
[13] https://www.theregister.com/2025/10/14/microsoft_october_2025_patch_tuesday/
[14] https://www.theregister.com/2026/01/08/rcisco_ise_bug_poc/
[15] https://www.theregister.com/2026/01/13/ai_python_library_bugs_allow/
[16] https://www.theregister.com/2026/01/08/cisa_oneview_powerpoint_bugs/
[17] https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2023-31096
[18] https://www.cve.org/CVERecord?id=CVE-2023-31096
[19] https://www.theregister.com/2025/10/14/microsoft_october_2025_patch_tuesday
[20] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20952
[21] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20953
[22] https://whitepapers.theregister.com/
The flaw, tracked as [1]CVE-2026-20805 and discovered by Microsoft's own threat intel team, allows an authorized attacker to leak a memory address from a remote ALPC port.
"Presumably, threat actors would then use the address in the next stage of their exploit chain – probably gaining arbitrary code execution," according to Trend Micro's Zero Day Initiative Head of Threat Awareness Dustin Childs' [2]analysis .
[3]
It's a medium-severity flaw, earning a 5.5 CVSS rating.
[4]
[5]
Shortly after Redmond pushed a patch, the US Cybersecurity and Infrastructure Security Agency [6]added CVE-2026-20805 to its [7]Known Exploited Vulnerabilities catalog , a step that means federal agencies must implement the fix by February 3. "This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise," the feds warned.
While we don't know who is abusing this hole, nor how widespread the exploitation is. Microsoft declined to answer our questions on the matter, so we'd suggest putting this patch at the top of the list.
[8]
"Vulnerabilities of this nature are commonly used to undermine Address Space Layout Randomization (ASLR), a core operating system security control designed to protect against buffer overflows and other memory-manipulation exploits," Kev Breen, senior director of cyber threat research at Immersive, told The Register .
"By revealing where code resides in memory, this vulnerability can be chained with a separate code execution flaw, transforming a complex and unreliable exploit into a practical and repeatable attack," he added, while also dinging Redmond for not disclosing which other components may be involved in such an exploit chain.
That omission, Breen said, "significantly" limits network defenders' "ability to proactively threat-hunt for related activity. As a result, rapid patching currently remains the only effective mitigation."
Two publicly known bugs
CVE-2026-20805 looks to be Microsoft's first zero-day bug of 2026, appearing on the first Patch Tuesday of the new year – and the patch dump is a whopper, with [9]112 Microsoft CVEs disclosed .
Of these, Microsoft lists two others as publicly known at the time of the release.
[10]
One of these, [11]CVE-2026-21265 , is a secure boot certificate expiration security feature bypass vulnerability, with a 6.4 CVSS rating. It's listed as publicly known because Microsoft [12]published this certificate expiration notice back in June 2025.
Some of the original certificates issued in 2011 are expiring soon, and operators of devices that use the soon-to-expire certificates need to update them – or lose the operating system's Secure Boot protections and security updates. As Childs noted, "while unlikely to be exploited, this bug could cause quite a bit of headaches for administrators."
[13]Frightful Patch Tuesday gives admins a scare with 175+ Microsoft CVEs, 3 under attack
[14]Patch Cisco ISE bug now before attackers abuse proof-of-concept exploit
[15]Popular Python libraries used in Hugging Face models subject to poisoned metadata attack
[16]CISA flags actively exploited Office relic alongside fresh HPE flaw
The other publicly known vulnerability, [17]CVE-2023-31096 , is a 7.8-rated elevation of privilege flaw in third-party Agere Modem drivers that ship with supported Windows versions. It's a non-Microsoft CVE that has to do with a flaw first documented in 2023 ( [18]CVE-2023-31096 ) and issued by MITRE.
During [19]October's patch-a-thon , Microsoft warned that this Agere Modem driver security hole had been made public, but not yet exploited, and said it would be removed in a future update. The future is now, and the drivers have been removed as of the January update.
A couple of other interesting bugs that Childs points out are these two, [20]CVE-2026-20952 (CVSS 7.7) and [21]CVE-2026-20953 (CVSS 7.4), both use-after-free Office flaws that can allow an unauthorized attacker to execute code locally.
"Another month with Preview Pane exploit vectors in an Office bug," Childs wrote. "While we are still unaware of any exploitation of these bugs, they keep adding up. It's only a matter of time until threat actors find a way to use these types of bugs in their exploits." ®
Get our [22]Tech Resources
[1] https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-20805
[2] https://www.zerodayinitiative.com/blog/2026/1/13/the-january-2026-security-update-review
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://www.cisa.gov/news-events/alerts/2026/01/13/cisa-adds-one-known-exploited-vulnerability-catalog
[7] https://www.cisa.gov/known-exploited-vulnerabilities-catalog
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://msrc.microsoft.com/update-guide/releaseNote/2026-Jan
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxoRDWmm5mFOdf0fxbFQAAA5g&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[11] https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2026-21265
[12] https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
[13] https://www.theregister.com/2025/10/14/microsoft_october_2025_patch_tuesday/
[14] https://www.theregister.com/2026/01/08/rcisco_ise_bug_poc/
[15] https://www.theregister.com/2026/01/13/ai_python_library_bugs_allow/
[16] https://www.theregister.com/2026/01/08/cisa_oneview_powerpoint_bugs/
[17] https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2023-31096
[18] https://www.cve.org/CVERecord?id=CVE-2023-31096
[19] https://www.theregister.com/2025/10/14/microsoft_october_2025_patch_tuesday
[20] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20952
[21] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20953
[22] https://whitepapers.theregister.com/
Re: maybe it fixes my pet-bug...
Jou (Mxyzptlk)
Update: Nope, did not fix it. But at least finally Server 2025 updates got separated from Windows 11 updates. [1]1.8 GB instead of [2]4.2 GB if fresh installed. Which means: 2.4 GB of that Windows 11 24h2 update package is densly packed utter crap most do not want.
[1] https://www.catalog.update.microsoft.com/Search.aspx?q=kb5073379
[2] https://www.catalog.update.microsoft.com/Search.aspx?q=kb5074109
Microsoft Update woes
ThatOne
I'd love to install the latest updates, but my vestigial Windows 11 decided to remain on 23H2. It just won't allow me to update any further... :-(
I really don't know how people manage to work seriously with this pile of burning refuse.
maybe it fixes my pet-bug...
I still have a hyper-v+deduplication scenario which causes corruption to the VMs residing on a deduped volume. Does not happen in many cases, but I have a few machines (with ECC RAM of course) where i can reliably exploit the issue. Since the machines crash with memory-error style too, maybe MAYBE I get lucky and my pet bug may be gone too? Will test :D.