Ten days later, Git on macOS still trusts the compromised eMudhra certificates
Source Entity
Hacker News
Apple has failed to revoke compromised eMudhra certificates in its macOS developer tools, leaving users vulnerable to man-in-the-middle attacks. Despite being notified, the latest macOS update did not address the issue and even reverted user-applied manual fixes.
The Security Oversight: Apple and the eMudhra Certificate Failure
The Vulnerability Explained
A significant security oversight has emerged regarding Apple's handling of compromised eMudhra certificates within its macOS developer toolchain. Despite receiving notification of the compromise on October 17th, Apple has failed to update its tools—including git, curl, and python3—to distrust the affected certificates. This leaves developers using these standard tools susceptible to man-in-the-middle (MITM) attacks, where malicious actors can intercept, view, or even alter encrypted HTTPS traffic.
Implications for the Developer Ecosystem
For developers, the implications are severe. Because tools like git rely on these certificates to establish secure connections, the integrity of code repositories is at risk. Attackers could potentially inject malicious code during git clone or pull operations or capture sensitive credentials, such as GitHub authentication tokens, as they are transmitted. This compromises the entire supply chain security for projects relying on these macOS-shipped binaries.
A Troubling Update Pattern
The situation worsened with the release of macOS 15.1 (version 27.2) on October 26th. Instead of patching the security flaw, the update failed to address the certificate trust issues entirely. More concerningly, the update reverted manual workarounds that power users had implemented to secure their environments, effectively forcing their systems back into a vulnerable state without their consent or knowledge.
Comparison with Industry Standards
The delay in Apple's response stands in stark contrast to the broader software community. Dozens of other open-source projects, many of which are maintained primarily by volunteers, successfully implemented and shipped fixes for the eMudhra incident days ago. The discrepancy between the rapid response of volunteer-led projects and the sluggishness of a trillion-dollar technology company highlights a potential breakdown in Apple's security patch management pipeline.
Broader Security Context and Future Outlook
This incident underscores the fragility of relying on pre-installed, system-level developer tools. When foundational utilities like curl and git are bundled with an operating system, users often assume they are maintained to the highest security standards. If Apple does not prioritize the revocation of these compromised certificates immediately, it risks eroding the trust of the professional developer community, who rely on these tools for high-stakes software deployment. Moving forward, this will likely lead to increased scrutiny of Apple's update cycle for third-party libraries and root certificate management.
Conclusion
The ongoing failure to resolve the eMudhra certificate issue on macOS represents a critical security gap. With users' credentials and code integrity currently exposed, the burden is now on Apple to issue a hotfix that not only addresses the trust store issue but also respects the security configurations of its users, ensuring that future updates do not overwrite essential manual protections.