sre-emudhra-ca-check
Skill4 starsChanged 23 days agoMITView on GitHub
Use to check whether a TLS/code-signing cert chains through one of the 8 eMudhra intermediate CAs revoked for private-key compromise, Oct 2026 (Mozilla bug 2083449): endpoints, cert files, k8s TLS secrets. Read-only; a match needs a gated reissue.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/sre-safety-gates.mdcCursor rule
- sre-awsSkill
- sre-azureSkill
- sre-capacity-planningSkill
- sre-change-safetySkill
- sre-chaos-engineeringSkill
- sre-cloud-cost-reviewSkill
- sre-database-triageSkill
- sre-datadogSkill
- sre-dependency-mappingSkill
- sre-diagnosticsSkill
- sre-dr-backup-testSkill
- sre-dynatraceSkill
- sre-emudhra-ca-checkSkill
- sre-engineerSkill
- sre-expiry-auditSkill
- sre-gcpSkill
- sre-incident-commandSkill
- sre-incident-communicationSkill
- sre-k8s-safe-remediationSkill
- sre-k8s-triageSkill
- sre-k8s-upgrade-autopilotSkill
- sre-message-queue-triageSkill
- sre-migration-safetySkill
- sre-observability-cost-cutterSkill
- sre-observability-query-cookbookSkill
- sre-oncall-auditSkill
- sre-oncall-handoffSkill
- sre-pagerduty-opsgenieSkill
- sre-php2shell-checkSkill
- sre-postmortem-templatesSkill
- sre-production-readinessSkill
- sre-prometheus-grafanaSkill
- sre-remediation-actionsSkill
- sre-runbook-templatesSkill
- sre-safety-gatesSkill
- sre-security-incident-triageSkill
- sre-service-mesh-triageSkill
- sre-slo-alertingSkill
- sre-slo-burn-rate-rulesSkill
- sre-terraformSkill
- sre-toil-reviewSkill
- sre-awsSkill
- sre-azureSkill
- sre-capacity-planningSkill
- sre-change-safetySkill
- sre-chaos-engineeringSkill
- sre-cloud-cost-reviewSkill
- sre-database-triageSkill
- sre-datadogSkill
- sre-dependency-mappingSkill
- sre-diagnosticsSkill
- sre-dr-backup-testSkill
- sre-dynatraceSkill
- sre-engineerSkill
- sre-expiry-auditSkill
- sre-gcpSkill
- sre-incident-commandSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
- Distinctive: line 34
Ask for scope: which endpoints (host:port), certificate files/bundles, and/or Kubernetes contexts and namespaces to check.
- Distinctive: line 35
Run the checker against every target:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
eMudhra intermediate CA compromise check
Safety gates (REQUIRED)
- Read-only diagnosis first.
- Propose each change with risk (low/med/high) and reversibility.
- Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
- Act only as approved, verify, and stop and escalate if anything gets worse.
Full rules: sre-safety-gates. This skill only reads certificates; it never issues, revokes or deploys one.
Background
In October 2026, eight eMudhra intermediate CAs (six TLS, two code-signing) turned out to have private keys weak enough to reconstruct from the public certificate — a key-generation script bug, not a theft. Google, Mozilla, Apple and Microsoft revoked trust in the affected intermediates and in emSign ECC Root CA - G3; Sectigo revoked its cross-signs of the same intermediates. eMudhra says its root keys and most production issuance were unaffected, but any certificate that does chain through one of the eight is signed by a key anyone could have derived, independent of whether it was ever misused.
Why this isn't covered by browser trust alone: Chrome, Firefox, Safari and Edge block these intermediates for people browsing to you in those browsers. They do nothing for your own service-to-service TLS, internal CAs, mobile apps with certificate pinning, CI/CD code-signing, or any client with its own trust store (curl, custom gRPC stacks, IoT, most non-browser software). This skill finds every certificate on your inventory that chains through the compromised intermediates so you can reissue it, regardless of what a browser would show a visitor.
This list goes stale. The bundled references/compromised-intermediates.json is a point-in-time snapshot (captured 2026-10-23) from Mozilla Bugzilla bug 2083449 and eMudhra's own advisory. Before relying on a clean result for a real decision, cross-check against CCADB and Mozilla's OneCRL, since the set of revoked serials can grow as cross-signs and backdated issuances are found.
Rules
- Check the whole chain, not just the leaf. The compromise is at the intermediate. A server can present a perfectly fine leaf signed by a compromised intermediate;
openssl s_client -showcertsis used unconditionally, never leaf-only. - Metadata only. Serial number and SHA-256 fingerprint of each certificate in the chain. Never read a private key, and for a Kubernetes
kubernetes.io/tlsSecret, check the serving endpoint instead of decodingtls.crtout of the Secret (the same object holdstls.key). - Bounded. Pass an explicit, finite list of targets (hosts, files, namespaces). No unbounded crawl of a CT log or the whole internet.
- A match is a finding, not an incident fix. Reissuing the certificate from a different, unaffected CA (or a non-compromised eMudhra intermediate after eMudhra's remediation) is a production change: hand it to
sre-change-safety, and if the certificate was actually relied on for authentication (mTLS, code-signing trust, not just serving TLS to the public internet), tosre-security-incident-triageas well.
Start here
- Ask for scope: which endpoints (host:port), certificate files/bundles, and/or Kubernetes contexts and namespaces to check. For Kubernetes, enumerate
kubernetes.io/tlsSecrets' endpoints withsre-k8s-triage's read-only commands first, then check those endpoints here — don't decode the Secret. Run the checker against every target:
bash scripts/emudhra-ca-check.sh --timeout 10 <host>[:<port>] ... bash scripts/emudhra-ca-check.sh --file <cert-or-bundle.pem> ...Output:
STATUS TARGET POSITION SUBJECT SHA256, one line per certificate in the chain (1(leaf),2,3, ...).STATUSisCOMPROMISED,OKorERROR. Exit 0 if every certificate on every target is OK, 1 if any isCOMPROMISED, 2 on a usage or connection error — the exit code is the worst single result, so always read the per-line STATUS when checking more than one target, the same convention assre-expiry-audit'scert-expiry.sh.- For code-signing trust (not a TLS endpoint): extract the signer's certificate chain from the signed artifact (e.g.
osslsigncode extract-signature,jarsigner -verify -verbose -certs, or your platform's equivalent) to a PEM file and run the same--filecheck against it. - For every
COMPROMISEDfinding, report it and stop — do not reissue, revoke or redeploy anything from this skill. Hand off:- Reissue: the owning team requests a new certificate from a CA not on the affected list, through
sre-change-safety(risk, reversibility, rollout plan — a TLS cert swap is usually low risk if paired with a monitoring check, but an mTLS client cert swap can break every caller at once, so verify no-downtime rollout first). - If the certificate authenticated something (mTLS between services, a code-signing trust anchor, an internal CA cross-sign) rather than just serving a public web page: treat it as a possible compromise of that trust relationship, not just an expiring-style housekeeping item, and loop in
sre-security-incident-triage.
- Reissue: the owning team requests a new certificate from a CA not on the affected list, through
Reading the result
COMPROMISEDon position1(leaf)means the leaf certificate itself was issued by (or in rare cases, is itself one of) a revoked intermediate — the certificate in active use is signed with a reconstructable key.COMPROMISEDon a later position means an intermediate further up the chain is affected, even if the leaf itself looks fine; the leaf still needs to be reissued under a clean chain.ERRORon a target means the check didn't run (connection failed, file unreadable, certificate unparseable) — it is not a clean result. Re-run it; don't report it as OK.- A target with no match against this skill's bundled list but a chain to
AAA Certificate Services,emSign Root TLS CA - G3,emSign Root CS CA - G3oremSign ECC Root CA - G3(the affected root hierarchies) is not itself compromised, but is worth a second look against CCADB/OneCRL directly, since the bundled list may not be current.
Output
- Scope checked (targets, files, namespaces) and anything that could not be checked, with the reason.
- One table:
status | target | position in chain | subject | sha256,COMPROMISEDrows first. - For each
COMPROMISEDfinding: whether it authenticates something beyond public-web TLS, and the hand-off (sre-change-safetyfor reissue, plussre-security-incident-triageif it authenticated a trust relationship).
Bundled scripts and references
bash scripts/emudhra-ca-check.sh [--timeout 10] [--data compromised-intermediates.json] [host[:port]|[ipv6]:port...] [--file cert.pem [cert.pem...]]
bash scripts/tests/run_tests.sh # offline tests- references/compromised-intermediates.json — the 8 eMudhra-issued + 8 Sectigo cross-signed revoked intermediates (serials, SHA-256 fingerprints, issuing root). Verify against CCADB/OneCRL before relying on it; update this file, not the script, when the authoritative list changes.
Last reviewed: 2026-10-23
SOURCES
Fetched and checked 2026-10-23.
- Mozilla Bugzilla bug 2083449 (eMudhra intermediate CA private-key compromise, revoked intermediates, serials and SHA-256 fingerprints): https://bugzilla.mozilla.org/show_bug.cgi?id=2083449
- eMudhra's own incident statement: https://emudhra.com/en/post/certificate-security-incident
- CCADB, the canonical cross-vendor registry of CA certificates and their status: https://www.ccadb.org/
openssl x509(-serial,-fingerprint -sha256): https://docs.openssl.org/3.0/man1/openssl-x509/ ·openssl s_client(-showcerts): https://docs.openssl.org/3.0/man1/openssl-s_client/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

