
The short answer to the question in the title is (as usual): „it depends.”.
At first glance, you may think that WSUS as a different product does not translate into Configuration Manager, which allows you to calmly leave the WSUS administrator to do the right thing. This will be the case if (happily in this case) the division of tasks does not force us to administer WSUS servers as well.
However, it will not always be that simple. The vulnerability will also affect Configuration Manager in case Software Updates functionality is enabled and we have at least one SUP server. Such a server is, of course, a typical WSUS server managed by Configuration Manager. As such, it obviously demands that the patch be installed, as the vulnerability is indeed dangerous[1].

Even worse is if the SUP server is the Primary Site Server itself. Then there is a direct threat of hostile takeover of the entire CM Site. This is probably the worst situation for a Configuration Manager administrator.

For the record, it should be noted that Configuration Manager's servers can also be clients of the WSUS server. When this one is successfully attacked, the (secondary) threat will affect all its clients. Then, however, domain controllers or other servers can be attacked just as easily.
It remains to be hoped that there are now no more WSUS servers without the required fix.
[1] https://www.cisa.gov/news-events/alerts/2025/10/24/microsoft-releases-out-band-security-update-mitigate-windows-server-update-service-vulnerability-cve
