How do I address the eMudhra certificate authority compromise in Upbound components?

Last updated: November 10, 2026

Goal

Know which Upbound components are affected by the eMudhra certificate authority compromise and upgrade them to patched versions.


Environment

  • Crossplane

  • Universal Crossplane (UXP)

  • Upbound Spaces

  • up CLI

  • Extensions

  • Hub

  • Spaces Connect agent

  • Marketplace and Registry

  • Upbound Cloud


Prerequisites

Access to upgrade the Upbound components you run.


Steps

Upbound's investigation is complete and patched releases are available for the affected components. Upgrade to the patched versions listed in the Upbound Trust Center eMudhra Certificate Update announcement as they fit your maintenance windows.

1. Check the patched versions for each component
Open the eMudhra Certificate Update announcement on the Upbound Trust Center. It is kept up to date with the current status of each component.

2. Upgrade Crossplane, UXP, Spaces, up CLI, Hub and the Spaces Connect agent
Upgrade each component you run to a patched version listed in the announcement.

3. Re-pull extensions
Patched releases are available for extensions, including FIPS-capable builds. Re-pull to update.

4. No action for Marketplace, Registry and Upbound Cloud
Marketplace and Registry are patched and need no action. Upbound Cloud is in progress. It is managed by Upbound, its public endpoints are confirmed unaffected, and no action is required.


Verify

Confirm that each component you run is on a version listed as patched in the Trust Center announcement.


Notes

Upbound's public endpoints are not affected
None of Upbound's public endpoints use certificates issued by the affected authority, so you should not experience any connectivity disruption reaching Upbound.

Unpatched software can keep trusting the revoked certificates
Software that validates TLS certificates against a bundled trust store can keep trusting the revoked eMudhra certificates until it is updated. If an attacker were also positioned on the network path, it could be tricked into accepting a forged certificate.

Services still using certificates tied to the revoked authority can become unreachable
As trust stores are updated across the broader ecosystem, any service still presenting a certificate tied to the revoked authority can become unreachable to clients that have already updated.


Related