This is the trust stores Cloudflare uses for CFSSL. It also includes the sources of the trust chain that can be built using the mkbundle utility from CFSSL.

Files:

.
├── ca-bundle.crt
├── ca-bundle.crt.metadata
├── certdata
│   └── trusted_roots
│       ├── froyo.pem
│       ├── gingerbread.pem
│       ├── honeycomb.pem
│       ├── ics.pem
│       ├── ios.pem
│       ├── kitkat.pem
│       ├── nss.pem
│       ├── osx.pem
│       ├── ubuntu.pem
│       └── windows.pem
├── int-bundle.crt
├── README.md

The ca-bundle.crt file contains trust anchors, including selected non-self-signed CA certificates. CFSSL uses the ca-bundle.crt.metadata when building bundles to assist in building bundles that need to verified in the maximum number of trust stores on different systems. The int-bundle.crt file contains a number of known intermediates; these are preloaded for performance reasons and occasionally updated as CFSSL finds more intermediates. If an intermediate isn't in this bundle, but can be found through following the AIA CA Issuers fields, it will be downloaded and eventually merged into here.

The trusted_roots directory contains the root stores from a number of systems. Currently, we have trust stores from

• NSS (Firefox, Chrome)
• OS X
• Windows
• Android 2.2 (Frozen Yogurt)
• Android 2.3 (Gingerbread)
• Android 3.x (Honeycomb)
• Android 4.0 (Ice Cream Sandwich)
• Android 4.4 (KitKat)

Use Go 1.27.3 or a later patched release for the release tools.

$ go install git.wntrmute.dev/kyle/goutils/cmd/certdump@v1.7.7
$ go install github.com/cloudflare/cfssl/cmd/...@latest
$ go install github.com/cloudflare/cfssl_trust/...@latest

The final bundles (i.e. ca-bundle.crt and int-bundle.crt) may be built as follows:

$ ./release.sh

Run this command from an up-to-date checkout containing the changes to publish, with no unrelated tracked or staged changes. It rolls new root and intermediate database snapshots, filters revoked and expiring certificates, and regenerates the bundles. It then commits the changes on a new release/<version> branch and immediately pushes both the branch and a trust-store-<version> tag to origin. Branch and tag push permission is required. Open a pull request for the release branch afterward; the script does not create one.

The content of 'ca-bundle.crt.metadata' is crucial to building ubiquitous bundle. Feel free to tune its content. Make sure the paths to individual trust root stores are correctly specified.

New roots and intermediates can be added using the same command, just by providing values for the NEW_ROOTS and NEW_INTERMEDIATES variables:

$ NEW_ROOTS="/path/to/root1 /path/to/root2" NEW_INTERMEDIATES="/path/to/int1 /path/to/int22" ./release.sh

To verify that an intermediate or root certificate is expiring or revoked without creating a release, the expiring command can be used from the project root directory.

To check for expiring or revoked intermediate certificates in the database provided in this repo:

$ cfssl-trust -d ./cert.db -b int expiring

To check for expiring or revoked root certificates:

$ cfssl-trust -d ./cert.db -b ca expiring

./cert.db which is specified as the database using the -d flag, contains both intermediate and root certificates. Any certificate database can be used here in place of ./cert.db

These calls to the expiring command will provide an output showing if there are any expiring or revoked certificates.

...
1 certificates expiring.
0 certificates revoked.

Following the eMudhra intermediate key compromise, AAA Certificate Services and emSign ECC Root CA - G3 were removed from database snapshot 2026.10.0, first published in tagged release trust-store-2026.10.1. Dated distrust records prevent future release rolls from including them. Historical releases and platform snapshots are preserved for reproducibility. emSign Root TLS CA - G3 and the eight compromised intermediate keys were absent from the bundles. The unaffected emSign C1, C3, and G1 roots remain trusted.

Removing these roots can also reject legitimate certificate chains. Database snapshot 2026.10.2 explicitly trusts 17 selected AAA-issued server-authentication CA certificates as non-self-signed anchors in ca-bundle.crt, preserving selected paths without restoring trust in the AAA root. Consumers must support terminating verification at these anchors (for example, OpenSSL requires -partial_chain); loading them only as untrusted intermediates is insufficient.

Consumers must deploy the updated bundle and restart services that load roots at startup. Rebuild Go services with Go 1.27.3 or Go 1.26.10 (or a later patched release) to also block the compromised keys during path validation.