rewindex

CompaniesAstronomerIncidents

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

No impact listedStatus: identifiedStarted Not resolved1 updatestatus.astronomer.io (opens in new tab)

Timeline of updates

  1. identified

    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 https://emudhra.we-have-a-problem.com/ (opens in new tab).

    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 (opens in new tab).

    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 (opens in new tab) 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 support@astronomer.io: mailto:support@astronomer.io. 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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.astronomer.io (opens in new tab).

Astronomer profileRecent Astronomer incidentsMarkdownJSON