Knowledge Base

AAA Certificate Services Root Removal

Overview

Microsoft removed the AAA Certificate Services Root CA from the Microsoft Root Store on October 25, 2026. Apple began removing the root from parts of macOS during the week of November 2, 2026. The root had already been removed from the Google Chrome and Mozilla trust stores in April 2025.

These changes are part of an emergency response to the eMudhra incident and the broader retirement of legacy root CAs. The AAA root had previously been used to cross-sign eMudhra CAs.

Sectigo previously stopped issuing certificates directly from the AAA root. AAA cross-signed CA certificates were used to support older devices while allowing certificates to be issued from modern hierarchies.

Expected Impact

For most current deployments, no impact is expected. Issues are more likely when an environment explicitly depends on AAA Certificate Services or forces a specific certificate path.

Environments That Should Be Reviewed

  • Applications or appliances using certificate, CA, or public-key pinning.
  • Private, custom, static, Java, application-specific, appliance, embedded-device, or container trust stores.
  • Legacy devices that may not contain newer Sectigo roots.
  • macOS applications that use different validation mechanisms, such as command-line tools versus Safari or Keychain.

Recommended Actions

  1. Confirm the affected client. Record the hostname or application, operating system and version, browser or application, device type, exact trust error, and whether all clients or only certain clients are affected.
  2. Inspect the public certificate chain. Determine the path used by the affected client from the leaf certificate through the issuing CA and intermediate certificates to the trusted root.
  3. Check whether AAA is required. Confirm whether the client-selected path actually terminates at AAA Certificate Services. Seeing AAA as one possible cross-signed path does not by itself mean the leaf certificate must be replaced.
  4. Review pinning. If the application pins AAA, a specific CA/intermediate, or a public key, remove the hard dependency and use the platform-supported trust-validation mechanism wherever possible.
  5. Review the trust store. Determine whether the application uses the operating-system trust store or its own CA bundle. Ensure the trust store is current and contains the applicable modern Sectigo trust anchor.
  6. Test after remediation. Retest with the affected application and platform. Different applications on the same device may construct different certificate paths.

Important macOS Note

Apple indicated that the initial change removes AAA from the underlying operating system, with full removal from Keychain expected to follow. During the transition, a command-line application may report AAA as untrusted while Safari behaves differently. Troubleshooting should therefore identify the exact application performing certificate validation.

Actions Not Recommended

  • Do not disable certificate validation.
  • Do not assume every trust error is caused by the AAA removal.
  • Do not immediately replace or reissue the certificate before validating the client-selected path.
  • Do not permanently restore AAA to a trust store as the default resolution.
  • Do not send private keys to Sectigo Support.

Information to Provide to Sectigo Support

  • Affected hostname or application.
  • Operating system and exact version.
  • Affected browser, application, appliance, or device.
  • Exact certificate or trust error.
  • Public certificate chain presented to the affected client.
  • Whether certificate/CA/public-key pinning is configured.
  • Whether the application uses a custom or static trust store.

Security reminder: Never provide private keys.

Frequently Asked Questions

Do I need to replace or reissue my Sectigo certificate?

Not by default. First confirm whether the affected client actually depends on AAA Certificate Services. A certificate-path or trust-store issue may be resolved without replacing the leaf certificate.

Will the removal affect every device?

No. Impact depends on the client, its trust store, its certificate-path processing, and whether it uses pinning or a custom trust configuration.

Should I manually add AAA back to the trust store?

This is not the recommended long-term resolution. The removals were intentional security decisions. The preferred approach is to remove the AAA dependency and use a currently supported trust path.

Why might Safari and a command-line tool behave differently?

During Apple’s rollout, operating-system validation and Keychain/Safari may not reflect the change at exactly the same stage. Always test the specific application used in production.


Related Sectigo Notices

Need assistance?

Contact our team for help with your purchase or issuing your certificate.

Live chat

Call us today