Apple blocks eMudhra certificates, but macOS git and curl may still trust compromised roots

Apple blocks eMudhra certificates, but macOS git and curl may still trust compromised roots

N
News Editor
2026-10-29 12:54:36
Apple has blocked the compromised eMudhra intermediate certificates, but a security research page said on Oct. 28, Taipei time, that several developer tools bundled with macOS may still trust the affected root certificates. The issue does not mean every Mac is fully compromised. The remaining exposure is centered on command-line and development environments that still read the system certificate file or ship with older trust stores, leaving room for man-in-the-middle attacks on some HTTPS connections if an attacker is on the network path. Apple’s support document says Safari and other apps that rely on Apple’s networking framework are protected, while tools such as curl, git, python3, ruby, perl, and openssl bundled with macOS or Xcode Command Line Tools may continue to accept the certificates until /etc/ssl/cert.pem is updated in a future system release. The research page said Apple was notified on Oct. 17 and that, as of Oct. 28, the tools still trusted the compromised certificates. It also said macOS 27.2, released on Oct. 26, did not fix the issue and could overwrite user-applied mitigations. Apple has published manual mitigation steps, and Python maintainers have urged users to upgrade certifi to 2026.10.19 and pip to 26.2.2. Developers using Macs for dependency fetching, code pushes, or CI workflows have been advised to inspect their local environments and trust chains.

Apple has blocked the compromised eMudhra intermediate certificates, but a security research page said on Oct. 28, Taipei time, that developer tools bundled with macOS, including git, curl, and python3, may still trust the affected root certificates. Safari and other apps that use Apple’s networking framework are protected, while parts of the terminal toolchain still appear exposed.

The report said this does not mean an entire Mac is fully compromised. The risk is concentrated in command-line and development environments that still read the system certificate file or ship with older root certificate lists. If an attacker is positioned on the network path, those HTTPS connections could, in theory, be exposed to man-in-the-middle, or MITM, attacks.

Safari is covered, but git and curl may still accept the certificates

Apple support documentation has said since Oct. 19 that devices automatically block the compromised eMudhra intermediate CA, and typical users who do not rely on terminal tools usually do not need to take extra action.

The same document also says that curl, git, python3, ruby, perl, and openssl bundled with macOS or Xcode Command Line Tools validate certificates against /etc/ssl/cert.pem. Until a future system update changes that file, those tools may continue to accept the affected certificates.

According to the research page, Apple was notified on Oct. 17. As of Oct. 28, the listed developer tools still trusted the compromised certificates. The page also said macOS 27.2, released on Oct. 26, did not fix the problem and may even overwrite manual mitigations applied by users, exposing them again. By contrast, many other projects maintained by volunteers had already patched the issue several days earlier.

Why the git exposure matters

For git, the impact is more concrete. When users run clone or pull over https:// remotes, an attacker could inject chosen code. Push content could also be altered, and credentials such as GitHub tokens could be intercepted in transit.

The research page provided a test command. If running git ls-remote against the test domain returns a certificate error, the machine is protected. If it still lists commits, the local git setup remains affected.

pip, certifi, and older bundled trust stores

Apple’s document also warned that some apps and tools ship with their own root certificate lists. Those do not follow Apple’s blocklist and do not read /etc/ssl/cert.pem.

A Python community notice urged users to upgrade certifi to 2026.10.19 and pip to 26.2.2, saying TLS clients may otherwise remain open to MITM attacks. Maintainers also stressed that older versions of pip load a bundled copy of certifi, so changing only the system trust store is not enough.

Reddit users also reported that /usr/bin/pip3 in the system path and the Python version bundled with Xcode still trusted the affected root certificates because they included an older certifi package. The report said those claims came from community and user feedback and had not been individually confirmed by Apple, but they were consistent with the broader warning that tools carrying their own certificate bundles need separate updates.

Apple’s manual mitigation steps

For administrators who want to act before a full fix arrives, Apple has published manual steps. After making a backup, users can remove the affected root certificates from /etc/ssl/cert.pem, including emSign ECC Root CA G3 and, if necessary, AAA Certificate Services.

Apple also warned that later macOS updates may replace that file with Apple’s own version. Until a system update includes a full fix, the file should be checked again after each upgrade.

Developers are being told to inspect CI and local environments

The research page said security teams should also review whether their CI setups use macOS runners and assess any supply-chain risk. In practice, developers can run the detection commands for git and curl, then upgrade pip and certifi in local or virtual environments to the safe versions.

For crypto projects that use Macs to fetch dependencies or push code, the gap in the trust chain has direct implications for source code and token security.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
13600

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.