I will say that I had the same or similar issue after upgrading to 26.0.1-ci.4. Upgrading to later versions (26.0.2) didn't fix the issue for me. In my configuration I had the 'Use LDAPS and bypass certificate errors' enabled, as I had not yet installed my internal Enterprise CA root and sub CA certificates to the docker container. Does this apply to your configuration?

I installed them using process documented here: https://docs.inedo.com/docs/installation/linux/installation-troubleshooting-docker-installations#cannot-connect-to-services-that-use-a-self-signed-or-an-internal-certificate-authority and this resolved the login issue for me. I still have an issue where the Active Directory Group used to grant access to my team no longer works, and I have had to grant my team members access individually.

Thanks for the response. Does that mean that the container is not susceptible to these vulnerabilities, or that you have assessed the vulnerabilities, but that this assessment status has not been replicated? Based on the package list (https://proget.inedo.com/containers/tags/ProductImages/inedo/proget/25.0.10-ci.9/packages), and the vulnerability details, it would appear that most may be relevant, at least from a package content perspective.

My organization is in the process of evaluating ProGet, which we would be looking to run as a Linux container. As part of the security evaluation we noticed that all of the vulnerabilities of the latest container version (https://proget.inedo.com/containers/tags/ProductImages/inedo/proget/25.0.10-ci.9/vulnerabilities at the time of writing), as well as earlier container versions listed, are labelled as "? Unassessed". Is there a reason for this?