Why is it less secure? You're adding an additional point of attack. Someone could compromise the CDN or they could stop operating and the domain will fall to someone else. (And it doesn't really matter if your CDNs security is better or worse than your own hosting security - if you use a CDN it adds security risk and does not take away the risk from whatever other hosting you're using.)
Why privacy? Your CDN can at the very least read the IPs of your visitors (+ they could add cookies, which will usually not happen but still is a possibility) and you may need to worry about legal issues (e.g. adding it to your GDPR statement).
Finally performance: I guess many people will use a CDN "because it's faster" - except it's not. In the past there used to be the argument that the JS may already be cached. However that's no longer the case as for security reasons browsers partition the cache based on the origin. It's always faster to fetch a resource over the same connection compared to opening up a new connection to a different host.
So: Don't fetch your JS from CDNs, just put it in your webspace and fetch it from there.