Live  /  Jamf  /  Incident

Jamf: Public disclosure of compromised intermediate certificate authority keys (eMudhra) affecting certificate trust across the internet

Jamf · jamf.comMinor incidentResolved2026-10-21 20:14 UTC
Public — what happened

Summary

Jamf said it began looking into the public disclosure of compromised eMudhra certificate authority keys, and how it might affect its products, at 14:05 UTC on 2026-10-21. The company said its engineering and security teams were applying mitigations, including changes to certificate trust settings where relevant. Jamf reported that all of its products and services stayed operational with no loss of functionality, and that customers did not need to take any action. The incident was marked resolved at 20:14 UTC the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Jamf against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Jamf: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Jamf report →

More from Jamf

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Jamf status & history page.

Related: Jamf status & history. SquidGrid is not affiliated with Jamf.