Ten days later, Git on macOS still trusts the compromised eMudhra certificates

1159 points · 399 comments on HN · read original →

Points and comments are a snapshot, not live.

Apple's git on macOS still trusts compromised eMudhra certificates ten days after notification.

Apple was notified of the eMudhra incident on October 17, but as of October 28, macOS developer tools including git, curl, and python3 still trust the compromised certificates. macOS 27.2, released October 26, did not fix the issue and reverted manual workarounds. Attackers can intercept HTTPS connections these tools make, potentially altering git clones, pushes, and credentials. Apple has protected Safari and apps using its networking framework. A manual workaround involves removing affected roots from /etc/ssl/cert.pem, but macOS updates may revert it. Dozens of other projects shipped fixes days ago.

What commenters are saying

Commenters are disappointed Apple hasn't pushed an emergency patch. A key point: macOS has two system CA stores, the keychain and /etc/ssl/cert.pem, and CLI tools check only the latter, which doesn't support revocation. Some debate the headline, arguing it wrongly frames git as the problem when macOS supplies the outdated certs. Others note manual workarounds may break valid sites using the same root CA. One user reports that the latest macOS 27.2 still shows the vulnerability with /usr/bin/curl. Apple's support article acknowledges the issue and advises users to remove root CAs manually.