How to fix: Expired Certificate in CA Chain
One or more intermediate or root certificates in the TLS chain have expired. An expired CA certificate in the chain causes strict verifiers to reject the entire chain even if the leaf certificate is still valid.
Why it matters
Browsers and API clients that enforce strict chain validation will refuse connections with an expired intermediate CA, breaking HTTPS for all affected users.
TLS chain validation requires every certificate from the leaf to the trust anchor to be within its validity period. If an intermediate CA certificate expires, the full chain is invalid regardless of the leaf certificate's expiry. This commonly happens when an intermediate CA renewed its own certificate but the server was not updated to serve the new chain.
How to fix it
- 1Update the certificate bundle on your server to include the renewed intermediate CA certificate.
- 2Verify the full chain: openssl verify -CAfile ca-bundle.pem server.crt
- 3Test the chain from the client perspective: openssl s_client -connect example.com:443 -showcerts
Code examples
Inspect chain expiry
openssl s_client -connect example.com:443 -showcerts < /dev/null 2>/dev/null | \
openssl storeutl -noout -text /dev/stdin | grep 'Not After'Verify chain
openssl verify -CAfile /etc/ssl/certs/ca-certificates.crt -untrusted chain.pem server.crtReferences
Detected automatically by VulnRadar. The check id is tls-cert-expired-ca-chain, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Expired Certificate in CA Chain?
- VulnRadar rates this high severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id tls-cert-expired-ca-chain, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Expired Certificate in CA Chain map to?
- It maps to CWE-298. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.