Astronomer incident

Security Update: Runtime Releases and Guidance for the eMudhra/emSign Certificate Issue

Notice

Ongoing since 12:01 AM UTC.

identified Oct 22, 2026, 12:01 AM UTC

Astronomer has released Runtime updates to address a publicly disclosed security vulnerability concerning private keys associated with eight eMudhra/emSign intermediate certificate authority (CA) certificates. For additional background, visit . **Scope and available updates** This advisory stems from an issue with a third-party certificate authority. Action required for customer-managed components depends on their specific certificate trust stores and verification mechanisms. The following Runtime releases incorporate certificate trust updates to mitigate this vulnerability: • **Runtime 13:** 13.12.1 • **Runtime 3.0:** 3.0-20 • **Runtime 3.1:** 3.1-23 • **Runtime 3.2:** 3.2-12 • **Runtime 3.3:** 3.3-10 For full details, please refer to the [Runtime release feed](https://www.astronomer.io/docs/runtime/runtime-release-feed). **Recommended customer actions** • Upgrade to the appropriate updated Runtime release for your environment. • Rebuild and redeploy custom images using the updated base image. Refer to our [mitigation guide](https://www.astronomer.io/docs/runtime/mitigate-emudhra-ca-compromise) for step-by-step instructions. • Audit customer-managed build pipelines and tooling, applying relevant vendor updates to certificate trust stores and signature verification components. • Ensure TLS and code-signature verification remain enabled. If updates cause validation failures, contact the endpoint owner or software publisher for replacement certificate or artifact guidance. Please note that Runtime updates address the trust components included within those specific releases. Customer-added dependencies, custom certificate bundles, and external tooling may require separate updates. **Support and further guidance** If you are unable to upgrade or require assistance determining the applicable next steps, please contact [**[email protected]**](mailto:[email protected]). Include your deployment model, Runtime version, and whether you maintain custom images or build pipelines. Additional mitigation guidance is currently being finalized. We will update this advisory as further details and Remote Execution releases are confirmed.

Started
Oct 22, 2026, 12:01 AM UTC
Resolved
Ongoing
Duration
● 1d 13h
Detected by Pingoru
Oct 22, 2026, 12:01 AM UTC

Update timeline

  1. identified Oct 22, 2026, 12:01 AM UTC

    Astronomer has released Runtime updates to address a publicly disclosed security vulnerability concerning private keys associated with eight eMudhra/emSign intermediate certificate authority (CA) certificates. For additional background, visit . **Scope and available updates** This advisory stems from an issue with a third-party certificate authority. Action required for customer-managed components depends on their specific certificate trust stores and verification mechanisms. The following Runtime releases incorporate certificate trust updates to mitigate this vulnerability: • **Runtime 13:** 13.12.1 • **Runtime 3.0:** 3.0-20 • **Runtime 3.1:** 3.1-23 • **Runtime 3.2:** 3.2-12 • **Runtime 3.3:** 3.3-10 For full details, please refer to the [Runtime release feed](https://www.astronomer.io/docs/runtime/runtime-release-feed). **Recommended customer actions** • Upgrade to the appropriate updated Runtime release for your environment. • Rebuild and redeploy custom images using the updated base image. Refer to our [mitigation guide](https://www.astronomer.io/docs/runtime/mitigate-emudhra-ca-compromise) for step-by-step instructions. • Audit customer-managed build pipelines and tooling, applying relevant vendor updates to certificate trust stores and signature verification components. • Ensure TLS and code-signature verification remain enabled. If updates cause validation failures, contact the endpoint owner or software publisher for replacement certificate or artifact guidance. Please note that Runtime updates address the trust components included within those specific releases. Customer-added dependencies, custom certificate bundles, and external tooling may require separate updates. **Support and further guidance** If you are unable to upgrade or require assistance determining the applicable next steps, please contact [**[email protected]**](mailto:[email protected]). Include your deployment model, Runtime version, and whether you maintain custom images or build pipelines. Additional mitigation guidance is currently being finalized. We will update this advisory as further details and Remote Execution releases are confirmed.

Your product runs on more than Astronomer

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →