eMudhra root CA issue: the default ngrok agent isn't affected

ngrok reported that it was not breached, but that compromised private keys for eight eMudhra intermediate certificate authorities could enable forged TLS certificates chaining to the widely trusted emSign ECC Root CA - G3 and AAA Certificate Services roots. The default ngrok agent configuration is unaffected because it pins ngrok’s own root certificate rather than relying on the host operating system’s trust store, and its software updates are independently signature-verified. Risk may apply to non-default configurations such as `connect_cas: host`, API calls, remote traffic-policy URLs, and HTTPS proxy connections, where a privileged network attacker could theoretically intercept traffic if the affected roots remain trusted. Users are advised to inspect configurations and scripts for these settings, update their operating system CA bundles, or upgrade to ngrok agent version 3.39.12, which blocks the affected roots; version 2 agents are end-of-life and require upgrading.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.