Skip to content

Aembit Cloud and Aembit Edge stop trusting compromised eMudhra certificates

In October 2026, a compromise exposed the private keys of eight emSign intermediate certificate authorities operated by eMudhra. Anyone holding those keys can issue certificates that chain to a widely trusted root certificate. Aembit Cloud and the Aembit releases in this entry reject certificates from these certificate authorities.

Aembit Cloud

Aembit Cloud no longer trusts the emSign ECC Root CA - G3 and AAA Certificate Services root certificates, so it rejects certificates from the compromised certificate authorities. Aembit applied this change to Aembit Cloud for you.

Aembit Edge

Upgrade each of the following that you run to the listed version or later:

  • Agent Proxy 1.35.6254, for the container image and the virtual machine installers. Agent Proxy rejects certificates from the compromised certificate authorities whatever the host trust store contains.
  • Aembit CLI 1.35.6254, which rejects them the same way.
  • Agent Controller 1.35.3776, for the Linux container image. On a virtual machine, Agent Controller uses the host operating system’s trust store, so it rejects these certificates only after the host stops trusting both root certificates.
  • Agent Injector 1.35.446
  • AWS Lambda Extension and AWS Lambda Layer 1.35.199, which include Agent Proxy 1.35.6254.
  • MCP Identity Gateway 1.35.6263
  • Aembit Secrets Operator 1.35.394
  • Helm Chart 1.35.575, which deploys Agent Proxy 1.35.6254, Agent Controller 1.35.3776, and Agent Injector 1.35.446 by default.
  • AWS ECS Terraform 1.35.5, which deploys Agent Proxy 1.35.6254 and Agent Controller 1.35.3776 by default.

Aembit Terraform Provider

Aembit Terraform Provider 1.35.1 and later reject certificates from the compromised certificate authorities.

MCP Identity Gateway 1.35.6263 security updates

MCP Identity Gateway version 1.35.6263 includes security updates.

A self-hosted MCP Identity Gateway can limit the MCP servers it connects to with the AEMBIT_NETWORK_ACCESS_POLICY environment variable. The default, any, allows MCP servers at any address. public allows only MCP servers at publicly reachable addresses. With public, MCP Identity Gateway does not use a proxy set in the host’s environment. If MCP Identity Gateway reaches MCP servers through a proxy, use any. See AEMBIT_NETWORK_ACCESS_POLICY.

This version also updates dependencies to address published security advisories.

For the latest available versions of these components, see the Edge Components Supported Versions page.

Other improvements also shipped in this build.

MCP Identity Gateway content inspection coverage

A security update for the MCP Identity Gateway broadens the MCP traffic that Content Security inspects.

The Gateway normalizes responses that MCP servers stream as server-sent events before inspection, so Content Security inspects those responses along with the rest of the session. The Gateway also applies the policy’s Fail Open on Error setting to requests it can’t read and to protocol errors. A policy set to fail closed blocks those requests.

These updates shipped in the same build as the MCP Identity Gateway 1.33.5654 release.