{"article":{"slug":"apples-git-still-trusts-the-compromised-emudhra-certificates","title":"Apple's git still trusts the compromised eMudhra certificates","subtitle":null,"summary":"Eleven days after Apple was notified of the eMudhra CA compromise, the git, curl and python3 Apple ships with macOS still trust the compromised certificates, and macOS 27.2 undid the manual workaround. The page explains why that lets attackers intercept HTTPS from these tools and what developers should do.","content_type":"announcement","language":"en","canonical_url":"https://emudhra.we-have-a-problem.com/apple.html","author":{"name":"Dennis Jackson","url":"https://github.com/dennisjackson","person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"we-have-a-problem.com","url":"https://emudhra.we-have-a-problem.com/","listing_slug":null,"listing":null},"topics":[{"name":"security","slug":"security","url":"https://listedarticles.com/topics/security"},{"name":"developer-tools","slug":"developer-tools","url":"https://listedarticles.com/topics/developer-tools"},{"name":"infrastructure","slug":"infrastructure","url":"https://listedarticles.com/topics/infrastructure"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":502,"reading_minutes":2,"published_at":"2026-10-28T00:00:00.000Z","added_at":"2026-10-29T20:14:23.162Z","updated_at":"2026-10-29T20:14:23.162Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/apples-git-still-trusts-the-compromised-emudhra-certificates","markdown_url":"https://listedarticles.com/articles/apples-git-still-trusts-the-compromised-emudhra-certificates.md","example":false,"citation":"Dennis Jackson, we-have-a-problem.com. \"Apple's git still trusts the compromised eMudhra certificates.\" 28 Oct 2026. https://emudhra.we-have-a-problem.com/apple.html (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://emudhra.we-have-a-problem.com/apple.html"},"body_markdown":"# Apple's git still trusts the compromised eMudhra certificates\n\n**28th October 2026**\n\nApple was notified of the eMudhra incident on 17th October. As of 28th October, the developer tools Apple ships with macOS, including git, curl and python3, still trust the compromised certificates.\n\nWorse, macOS 27.2, released on 26th October, did not fix the issue and undid the workaround that users had applied by hand, leaving them vulnerable again.\n\nMeanwhile, [dozens of other projects](https://emudhra.we-have-a-problem.com/#developers), many run by volunteers, shipped fixes days ago.\n\n## [Why does this matter?](#why)\n\nAnyone can intercept any HTTPS connection these tools make.\n\nFor git, that means clones and pulls from `https://` remotes can deliver attacker-chosen code, pushes can be altered in transit, and your credentials, such as GitHub tokens, can be intercepted.\n\nTo check whether your git is affected, run:\n\n```\ngit ls-remote https://git-emudhra.we-have-a-problem.com/check.git\n```\n\nA certificate error means your git is protected. If git lists a commit, your git is affected. Your connections to GitHub, or any other `https://` git remote, can be intercepted and tampered with.\n\nTo see an attack end to end, run the command below in a temporary directory. It clones a repository from a test server impersonating GitHub. The `-c` option redirects `github.com` to our test server for this one command only. The server presents a `github.com` certificate issued by one of the compromised eMudhra intermediates.\n\n```\ngit -c http.curloptResolve=github.com:443:15.235.19.186 clone https://fake-user@github.com/galadran/emudhra-git-test\n```\n\nA patched git will refuse with a certificate error. If the clone succeeds, you'll see a `README.md` starting with **INTERCEPTED**.\n\nA real attacker would not need the extra option. Anyone on the network path between you and GitHub can redirect your traffic themselves.\n\nYou can replace the demo repository with any other, public or private. Keep the `fake-user@` prefix. Without it, git would send your GitHub credentials to the test server. For example:\n\n```\ngit -c http.curloptResolve=github.com:443:15.235.19.186 clone https://fake-user@github.com/Homebrew/brew\n```\n\ncurl, python3 and the other tools Apple ships are affected in the same way. To check curl, run:\n\n```\ncurl https://dv-g3b-noct-emudhra.we-have-a-problem.com/\ncurl https://dv-g3b-aaa-noct-emudhra.we-have-a-problem.com/\n```\n\nA certificate error means curl is protected.\n\n## [What should Apple do?](#ask)\n\nApple has already protected Safari and other apps built on its networking framework.\n\nApple needs to ship a fix for macOS developers as soon as possible, for example by removing the affected roots from `/etc/ssl/cert.pem`.\n\n## [What can developers do in the meantime?](#workaround)\n\nThe affected roots can be removed by hand. The [macOS workaround](https://emudhra.we-have-a-problem.com/#macos-curl) on the main page walks through the steps. Apple's [guidance](https://support.apple.com/en-us/149555) states that macOS updates may revert the fix, so developers need to repeat the checks above and the workaround after every update until Apple ships a fix.\n\nSecurity teams should also consider whether macOS runners are used in their CI or other build infrastructure and evaluate the supply chain risk.\n\n---\n\nSite published by [Dennis Jackson](https://github.com/dennisjackson). This site is the work of [many contributors](https://github.com/galadran/we-have-a-problem.com/graphs/contributors) from the community. The source is on [GitHub](https://github.com/galadran/we-have-a-problem.com) and PRs are welcome. Licensed under the [Apache License, Version 2.0](https://github.com/galadran/we-have-a-problem.com/blob/main/LICENSE).\n","body_html":"<h1 id=\"apple-s-git-still-trusts-the-compromised-emudhra-certificates\">Apple&#39;s git still trusts the compromised eMudhra certificates</h1>\n<p><strong>28th October 2026</strong></p>\n<p>Apple was notified of the eMudhra incident on 17th October. As of 28th October, the developer tools Apple ships with macOS, including git, curl and python3, still trust the compromised certificates.</p>\n<p>Worse, macOS 27.2, released on 26th October, did not fix the issue and undid the workaround that users had applied by hand, leaving them vulnerable again.</p>\n<p>Meanwhile, <a href=\"https://emudhra.we-have-a-problem.com/#developers\" rel=\"nofollow ugc noopener\">dozens of other projects</a>, many run by volunteers, shipped fixes days ago.</p>\n<h2 id=\"why-does-this-matter\"><a href=\"#why\">Why does this matter?</a></h2>\n<p>Anyone can intercept any HTTPS connection these tools make.</p>\n<p>For git, that means clones and pulls from <code>https://</code> remotes can deliver attacker-chosen code, pushes can be altered in transit, and your credentials, such as GitHub tokens, can be intercepted.</p>\n<p>To check whether your git is affected, run:</p>\n<pre><code>git ls-remote https://git-emudhra.we-have-a-problem.com/check.git</code></pre>\n<p>A certificate error means your git is protected. If git lists a commit, your git is affected. Your connections to GitHub, or any other <code>https://</code> git remote, can be intercepted and tampered with.</p>\n<p>To see an attack end to end, run the command below in a temporary directory. It clones a repository from a test server impersonating GitHub. The <code>-c</code> option redirects <code>github.com</code> to our test server for this one command only. The server presents a <code>github.com</code> certificate issued by one of the compromised eMudhra intermediates.</p>\n<pre><code>git -c http.curloptResolve=github.com:443:15.235.19.186 clone https://fake-user@github.com/galadran/emudhra-git-test</code></pre>\n<p>A patched git will refuse with a certificate error. If the clone succeeds, you&#39;ll see a <code>README.md</code> starting with <strong>INTERCEPTED</strong>.</p>\n<p>A real attacker would not need the extra option. Anyone on the network path between you and GitHub can redirect your traffic themselves.</p>\n<p>You can replace the demo repository with any other, public or private. Keep the <code>fake-user@</code> prefix. Without it, git would send your GitHub credentials to the test server. For example:</p>\n<pre><code>git -c http.curloptResolve=github.com:443:15.235.19.186 clone https://fake-user@github.com/Homebrew/brew</code></pre>\n<p>curl, python3 and the other tools Apple ships are affected in the same way. To check curl, run:</p>\n<pre><code>curl https://dv-g3b-noct-emudhra.we-have-a-problem.com/\ncurl https://dv-g3b-aaa-noct-emudhra.we-have-a-problem.com/</code></pre>\n<p>A certificate error means curl is protected.</p>\n<h2 id=\"what-should-apple-do\"><a href=\"#ask\">What should Apple do?</a></h2>\n<p>Apple has already protected Safari and other apps built on its networking framework.</p>\n<p>Apple needs to ship a fix for macOS developers as soon as possible, for example by removing the affected roots from <code>/etc/ssl/cert.pem</code>.</p>\n<h2 id=\"what-can-developers-do-in-the-meantime\"><a href=\"#workaround\">What can developers do in the meantime?</a></h2>\n<p>The affected roots can be removed by hand. The <a href=\"https://emudhra.we-have-a-problem.com/#macos-curl\" rel=\"nofollow ugc noopener\">macOS workaround</a> on the main page walks through the steps. Apple&#39;s <a href=\"https://support.apple.com/en-us/149555\" rel=\"nofollow ugc noopener\">guidance</a> states that macOS updates may revert the fix, so developers need to repeat the checks above and the workaround after every update until Apple ships a fix.</p>\n<p>Security teams should also consider whether macOS runners are used in their CI or other build infrastructure and evaluate the supply chain risk.</p>\n<hr />\n<p>Site published by <a href=\"https://github.com/dennisjackson\" rel=\"nofollow ugc noopener\">Dennis Jackson</a>. This site is the work of <a href=\"https://github.com/galadran/we-have-a-problem.com/graphs/contributors\" rel=\"nofollow ugc noopener\">many contributors</a> from the community. The source is on <a href=\"https://github.com/galadran/we-have-a-problem.com\" rel=\"nofollow ugc noopener\">GitHub</a> and PRs are welcome. Licensed under the <a href=\"https://github.com/galadran/we-have-a-problem.com/blob/main/LICENSE\" rel=\"nofollow ugc noopener\">Apache License, Version 2.0</a>.</p>","headings":[{"level":1,"text":"Apple's git still trusts the compromised eMudhra certificates","id":"apple-s-git-still-trusts-the-compromised-emudhra-certificates"},{"level":2,"text":"Why does this matter?","id":"why-does-this-matter"},{"level":2,"text":"What should Apple do?","id":"what-should-apple-do"},{"level":2,"text":"What can developers do in the meantime?","id":"what-can-developers-do-in-the-meantime"}]}}