You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Base Image] nanoserver: ETA for base image rebuild with updated Disallowed CTL (eMudhra CA compromise / CVE-2026-111943) #659
What is your question?
A clear and concise description of what your question is. If you have bug/blocker, please open a 'Bug Report' issue instead.
On October 20, standard Windows hosts automatically received the updated Certificate Trust List (CTL) blocking the eMudhra / Sectigo intermediate certificates via background updates. However, because Windows Server containers (such as nanoserver) lack background Windows Update servicing, they do not automatically receive these updates.
In light of this, we have two key questions regarding Microsoft's support and recommended practices:
Will Microsoft issue an out-of-band rebuilt image for mcr.microsoft.com/windows/nanoserver to include the updated Disallowed certificate store, or will this update be held until the upcoming Patch Tuesday on November 10, 2026?
In the interim, what is the recommended procedure for importing the Disallowed CTL into offline or minimal nanoserver container images within Docker build pipelines prior to the release of an updated base image?
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
Updated base images are available now, so you don't need to wait for November 10. On October 26, 2026, Microsoft released an out-of-band (OOB) update that is "intended for devices that do not receive current certificate trust list (CTL) updates, including updates to the list of untrusted certificates." Refreshed nanoserver and servercore images built on this update are published on MCR, and the ltsc tags already point to them:
Recommended next step: pull the updated base image and rebuild. If you pin to a version tag or digest, move to the tag above. This replaces the need for a build-time import of the Disallowed list.
docker pull mcr.microsoft.com/windows/nanoserver:ltsc2025
docker image inspect mcr.microsoft.com/windows/nanoserver:ltsc2025 --format "{{.OsVersion}}"# Expect 10.0.26100.33674 (10.0.20348.5773 for ltsc2022, 10.0.17763.9378 for ltsc2019)
One note: applications that ship their own trust store (for example, Java's cacerts or Python's certifi) don't use the Windows certificate stores, so they need their own update.
If anything in your pipeline prevents you from rebasing right away, let us know and we can help with an interim approach.
Reacted by Xun Jiang/Bruce Jiang and Hervé Le Meur
Activity
github-actions commentedon Oct 23, 2026
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
smiezah-msft commentedon Oct 27, 2026
Hi Xun Jiang/Bruce Jiang (@blackpiglet), thanks for raising this and for the clear write-up.
Updated base images are available now, so you don't need to wait for November 10. On October 26, 2026, Microsoft released an out-of-band (OOB) update that is "intended for devices that do not receive current certificate trust list (CTL) updates, including updates to the list of untrusted certificates." Refreshed
nanoserverandservercoreimages built on this update are published on MCR, and theltsctags already point to them:10.0.26100.33674ltsc202510.0.20348.5773ltsc202210.0.17763.9378ltsc2019,1809Recommended next step: pull the updated base image and rebuild. If you pin to a version tag or digest, move to the tag above. This replaces the need for a build-time import of the Disallowed list.
One note: applications that ship their own trust store (for example, Java's
cacertsor Python'scertifi) don't use the Windows certificate stores, so they need their own update.If anything in your pipeline prevents you from rebasing right away, let us know and we can help with an interim approach.