Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue

LaunchDarkly Status · Resolved

Status

Resolved

Severity

Unknown

Started

Oct 21, 2026 18:34 UTC

Resolved

Nov 03, 2026 03:40 UTC

Timeline

Resolved · LaunchDarkly Status · Nov 03 03:40 UTC

Completed

The scheduled maintenance has been completed.

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue →
Update · LaunchDarkly Status · Oct 21 18:40 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue →
Update · LaunchDarkly Status · Oct 21 18:40 UTC

THIS IS A SCHEDULED EVENT Oct 21, 11:40 PDT  -  Nov 2, 19:40 PST

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue →
Update · LaunchDarkly Status · Oct 21 18:34 UTC

Scheduled

We currently have no indication that LaunchDarkly-hosted services or customer data are impacted by the publicly-disclosed compromised intermediate CA certificates from eMudhra (https://emudhra.we-have-a-problem.com/). This guidance applies to all LaunchDarkly instances: Commercial, EU, and Federal.LaunchDarkly has already taken precautionary steps to secure our platform and has released updated versions of the Relay Proxy and SDKs used by our customers. We continue to monitor the situation and patch all non-critical services.We highly recommend that customers immediately take the following steps to secure the network connection between their systems and LaunchDarkly:- Update LaunchDarkly SDKs and Relay Proxy listed below to the latest version provided- Ensure your application hosts disallow the compromised CAs- Follow publicly-documented remediation steps for your application infrastructure to disallow compromised CAs: https://emudhra.we-have-a-problem.com/LaunchDarkly SDKsOnly the following LaunchDarkly SDKs are affected by this issue and require an update to the versions listed.- Server-side SDK for Python (9.18.3): https://github.com/launchdarkly/python-server-sdk/releases/tag/9.18.3- Server-Side SDK for Erlang/Elixir (3.12.1): https://github.com/launchdarkly/erlang-server-sdk/releases/tag/v3.12.1- OpenFeature provider for the Server-Side SDK for Python (0.8.3): https://github.com/launchdarkly/openfeature-python-server/releases/tag/0.8.3- SDK OTEL integration for the Python server side SDK (1.3.0): https://github.com/launchdarkly/python-server-sdk-otel/releases/tag/1.3.0- Observability and Session Replay SDK for Python (1.3.4): https://github.com/launchdarkly/observability-sdk/releases/tag/launchdarkly-observability-python-1.3.4LaunchDarkly Relay Proxy- Relay Proxy (8.23.2): https://github.com/launchdarkly/ld-relay/releases/tag/v8.23.2- Relay Proxy Helm Chart (3.11.3): https://github.com/launchdarkly/ld-relay-helm/releases/tag/3.11.3We will provide further updates as the situation develops. You can always view our trust center (https://app.vanta.com/launchdarkly.com/trust/gu6fblhdgsyexg8g2xsj0) for the latest updates, as well

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue →
Update · LaunchDarkly Status · Oct 21 18:34 UTC

Scheduled

We currently have no indication that LaunchDarkly-hosted services or customer data are impacted by the publicly-disclosed compromised intermediate CA certificates from eMudhra (https://emudhra.we-have-a-problem.com/). This guidance applies to all LaunchDarkly instances: Commercial, EU, and Federal.LaunchDarkly has already taken precautionary steps to secure our platform and has released updated versions of the Relay Proxy and SDKs used by our customers. We continue to monitor the situation and patch all non-critical services.We highly recommend that customers immediately take the following steps to secure the network connection between their systems and LaunchDarkly:- Update LaunchDarkly SDKs and Relay Proxy listed below to the latest version provided- Ensure your application hosts disallow the compromised CAs- Follow publicly-documented remediation steps for your application infrastructure to disallow compromised CAs: https://emudhra.we-have-a-problem.com/LaunchDarkly SDKsOnly the following LaunchDarkly SDKs are affected by this issue and require an update to the versions listed.- Server-side SDK for Python (9.18.3): https://github.com/launchdarkly/python-server-sdk/releases/tag/9.18.3- Server-Side SDK for Erlang/Elixir (3.12.1): https://github.com/launchdarkly/erlang-server-sdk/releases/tag/v3.12.1- OpenFeature provider for the Server-Side SDK for Python (0.8.3): https://github.com/launchdarkly/openfeature-python-server/releases/tag/0.8.3- SDK OTEL integration for the Python server side SDK (1.3.0): https://github.com/launchdarkly/python-server-sdk-otel/releases/tag/1.3.0- Observability and Session Replay SDK for Python (1.3.4): https://github.com/launchdarkly/observability-sdk/releases/tag/launchdarkly-observability-python-1.3.4LaunchDarkly Relay Proxy- Relay Proxy (8.23.2): https://github.com/launchdarkly/ld-relay/releases/tag/v8.23.2- Relay Proxy Helm Chart (3.11.3): https://github.com/launchdarkly/ld-relay-helm/releases/tag/3.11.3We will provide further updates as the situation develops.

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue →