GlobalSign: Issuing CA certificate with wrong notBefore date

RESOLVED INVALID GlobalSign nv-sa

This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.

AI Summary

GlobalSign reported that, during a regular review of certificates, it discovered one issuing CA certificate that had been issued with an incorrect notBefore date. GlobalSign stated that it would provide an incident report by Friday, February 26, 2021. A third party (Sectigo) commented that the intended notBefore year was likely 2021 rather than 2020, but also stated that it did not see a policy violation and suggested resolving the bug as INVALID. Mozilla agreed with that assessment and closed the bug as INVALID. The bug is currently marked RESOLVED with resolution INVALID.

Model: gpt-5.4-nano Generated: 2026-06-13 21:31 UTC Revised: 2026-06-16 18:55 UTC Confidence: 0.86 4 comments

Chronology

2021-02-23 GlobalSign discovered an issuing CA certificate was issued with an incorrect notBefore date during a regular certificate review.

Thread Activity

2021-02-23 GlobalSign nv-sa — GlobalSign said it discovered one issuing CA certificate issued with a wrong notBefore date and that it would provide an incident report by February 26, 2021.
2021-02-23 Sectigo — Sectigo suggested the notBefore year likely should have been 2021 instead of 2020, and recommended resolving the bug as INVALID because it did not see a policy violation.
2021-02-23 Mozilla representative — Mozilla agreed and closed the bug as INVALID.

Participants

GlobalSign nv-sa Sectigo Mozilla representative

External References

Original Bugzilla Case crt.sh

Similar Local Cases

#1690807 RESOLVED Incident Self Reported Incident Opened 2021-02-04 · Closed 2023-02-22 · 100% similar

GlobalSign: RSA-1024 leaf certificate issued after 2013-12-31

AI Summary CA Owner

#1664328 RESOLVED Incident Self Reported Incident Opened 2020-09-10 · Closed 2023-02-22 · 100% similar

GlobalSign: SHA-256 hash algorithm used with ECC P-384 key

AI Summary CA Owner

#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 96% similar

GlobalSign: Invalid stateOrProvinceName and locality pair

AI Summary CA Owner

#1649937 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 96% similar

GlobalSign: Incorrect OCSP Delegated Responder Certificate

AI Summary CA Owner

#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 95% similar

GlobalSign: Invalid countryName

AI Summary CA Owner

#1917896 RESOLVED Self Reported Incident Opened 2024-09-10 · Closed 2025-03-18 · 94% similar

GlobalSign: Incorrect whois information for TLD

AI Summary CA Owner

#1575880 RESOLVED Self Reported Incident Revocation Issue Validation Issue Opened 2019-08-22 · Closed 2023-02-22 · 88% similar

GlobalSign: SSL Certificates with US country code and invalid State/Prov

AI Summary CA Owner

#1658932 RESOLVED Self Reported Incident Opened 2020-08-13 · Closed 2023-02-22 · 88% similar

GlobalSign: Incorrect Jurisdiction of Incorporation information for Japan

AI Summary CA Owner