Taktile incident

Response to eMudhra certificate compromise

Resolved after 7 hours 35 minutes, on October 21, 2026.

resolved Oct 21, 2026, 05:13 PM UTC

Based on our investigation, none of our systems are affected, and we did not observe any exploitation. We will continue rolling out updates and monitoring the situation as it evolves.

Started
Oct 21, 2026, 09:37 AM UTC
Resolved
Oct 21, 2026, 05:13 PM UTC
Duration
7h 35m
Detected by Pingoru
Oct 21, 2026, 09:37 AM UTC

Update timeline

  1. investigating Oct 21, 2026, 09:37 AM UTC

    We are assessing indirect exposure to compromised eMudhra certificate authorities through trusted certificates used by some of our services. Taktile’s own TLS certificates are not issued by eMudhra. We are reviewing the affected trust configuration and the changes needed to remove this exposure.

  2. monitoring Oct 21, 2026, 02:20 PM UTC

    Mitigations for endpoint devices are being enforced. Mitigations for intermediary Python services are also being rolled out and over half way complete.

  3. resolved Oct 21, 2026, 05:13 PM UTC

    Based on our investigation, none of our systems are affected, and we did not observe any exploitation. We will continue rolling out updates and monitoring the situation as it evolves.

Your product runs on more than Taktile

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →