This is not something we control. The image is loaded from inside a page, like any usual image. What img.shields.io needs to do is set the appropriate headers on their responses. Usually for these kind of services a complete wildcard
* access is common. Looking at their bugtracker they seem to have some issues and have delayed deploying fixes to remedy this on some browsers.
From our side there's nothing we can do, because we cannot add the headers your chrome browser complains about when simply linking it from within a post. I also don't see any specific reason why Chrome would complain about this recently as many of the reports stem from the stage it introduced isolation 😕