NEW Solace Fall ’26 Edition: Unbound is now live See the release

Last Updated: November 9, 2026 at 9:00AM (EST)
Status: Resolved – Solace Product Updates Released

Solace is aware of the recently reported root certificates that are no longer trusted (emSign ECC Root CA – G3, emSign Root CA – C1, and emSign ECC Root CA – C3) and has completed a full analysis of our exposure: eMudhra: Private key compromise of Intermediate Certificates. All products have been updated to resolve this issue. Solace strongly recommends upgrading all affected products to resolve this issue.

Impacted Products

The following products are impacted by this vulnerability.  No other Solace products are impacted.

Solace Event Broker

  • All Solace Event Broker versions prior to 10.26.9.13589, 10.26.0.9163, 10.25.0.402, and 10.8.1.604 contain compromised emSign root certificates in the list of default trusted certificate authorities. A broker that makes outbound TLS connections would accept a server certificate chaining to one of these compromised roots.
  • Solace resolved this vulnerability in broker releases 10.26.9.13589, 10.26.0.9163, 10.25.0.402, and 10.8.1.604, on October 27, 2026. Solace strongly recommends upgrading all affected brokers to resolve this issue.
  • For customers unable to upgrade immediately: The updated standard domain certificate authority (CA) list, which excludes the affected emSign certificates, is available only in the fixed event broker releases listed above. An upgrade is required to obtain the updated standard list. Customers considering disabling the standard CA list before upgrading should be aware of the following:
    • Standard Domain CA list — Individual CAs cannot be removed from the standard list. The list can only be disabled in its entirety, in which case customers must manually configure all CAs required for their outbound TLS connections. Outbound TLS connections on the event broker can include: REST Delivery Points (RDPs), Message VPN bridges, Replication, Multi-Node Routing (MNR) connections, Dynamic Message Routing (DMR) connections, Kafka senders and receivers, LDAP over TLS, OAuth provider connections, Network Time Protocol (NTP) with Network Time Security (NTS), syslog forwarding over TLS, and TLS Solace Element Management Protocol (SEMP) connections made through the Broker Manager wizards.
    • High-availability event brokers — In high-availability (HA) deployments using SEMP over TLS (enabled by default in Solace Cloud), at least one domain CA must be configured to keep the SEMP service operational. These CAs must include the CA required to validate the HA mate’s server certificate to preserve SEMP communication between mates. Disabling the standard list without configuring any CAs will cause the SEMP service to become unavailable on the next restart or upgrade. In Kubernetes deployments (including Solace Cloud), this SEMP outage will trigger repeated event broker restarts.
    • After upgrading — Solace recommends that customers who temporarily disabled the standard CA list re-enable it to use the updated list.

Solace Cloud Console

  • Numerous Solace Cloud console components contained the affected emSign root certificates, however many do not initiate outgoing connections so are not exposed to this vulnerability. Solace has completed patching all affected services on November 3, 2026.

Solace Agent Mesh

  • All Solace Agent Mesh versions contain the affected emSign root certificates in the list of trusted certificate authorities.
  • Most Solace Agent Mesh outbound connections, including LLM connections, include the affected emSign root certificates.  This was resolved in Solace Agent Mesh v2.455.0 and is available now.
  • The Solace Agent Mesh Broker client library and Mac desktop app are also affected.  Solace released Agent Mesh 2.493.0 on October 28, 2026 to resolve these issues.

Solace Micro-Integrations

  • The docker image of all versions of all Solace Micro-Integrations contain an OpenJDK JRE which contains the affected emSign root certificates in the list of trusted certificate authorities.
  • A work-around is available from OpenJDK.  Refer to https://openjdk.org/emudhra for details.
  • Solace has resolved this exposure in all Micro-Integrations.  These releases completed on November 1, 2026.

Solace Schema Registry

  • Solace Schema Registry versions 1.0.0 through 1.1.2 are impacted. Solace has released version 1.1.3 to resolve this vulnerability on November 3, 2026.

Solace Broker MCP

  • Solace Broker MCP v1.0.0 is impacted.
  • Solace released v1.1.0 to resolve this vulnerability on October 29, 2026.

Solace Broker Terraform Providers (Broker and Appliance)

  • Solace Broker Terraform Providers (Broker and Appliance) v1.3.1 and earlier are impacted. 
  • Solace released Broker Terraform Providers (Broker and Appliance) v1.4.0 on October 28, 2026 to resolve this vulnerability.
  • Solace Cloud Terraform Provider 0.2.4 and earlier are impacted
  • Solace released Cloud Terraform Provider 0.2.6 to resolve this vulnerability on October 28, 2026.

Nisshi Diskless Streaming for Apache Kafka®

  • Versions 0.7.0 and earlier contain the affected emSign root certificates in the list of trusted certificate authorities.
  • Version 0.8.1 was released on October 28, 2026 to address this vulnerability.