← GlobalSign nv-sa cases
Bugzilla #1552586 Self Reported Incident Certificate Misissuance

GlobalSign: 4 Misissued certificates with invalid CN

RESOLVED FIXED 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 a compliance issue involving four misissued SSL certificates with invalid Common Names (CN). The CA became aware of the problem through its post-issuance compliance checker on May 17, 2019. Following the detection, GlobalSign promptly revoked the certificates and initiated an investigation. The root cause was identified as a missing check for CN/SAN validation in a specific scenario involving a deprecated API. GlobalSign has since implemented code updates to ensure proper validation and is conducting a thorough review of its systems to prevent future occurrences.

Model: gpt-4o-mini Generated: 2026-06-13 18:14 UTC Revised: 2026-06-16 18:46 UTC Confidence: 0.90 18 comments
Chronology
  1. GlobalSign detected misissued certificates through its compliance checker.
  2. Certificates were revoked and an investigation was initiated.
  3. GlobalSign identified the root cause related to a missing validation check.
  4. GlobalSign implemented updates to ensure proper validation checks.
Thread Activity
  1. Community commenter — GlobalSign's compliance checker alerted us to the problem in 4 SSL certificates.
  2. Community commenter — We rolled out updated code that now properly checks the CN and SAN values.
  3. Community commenter — We verified that all proper checks are in place for AEG certificate requests.
  4. Fastly representative — It appears that all questions have been answered and remediation is complete.
Participants
Community commenter Fastly representative
External References
Similar Local Cases
#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 100% similar
GlobalSign: Invalid countryName
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 100% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1524877 RESOLVED Certificate Misissuance Opened 2019-02-03 · Closed 2023-02-22 · 100% similar
GlobalSign: IP in dnsName
#1547691 RESOLVED Certificate Misissuance Opened 2019-04-29 · Closed 2023-02-22 · 100% similar
GlobalSign: AT&T SSL certificates without the AIA extension
#1554259 RESOLVED Self Reported Incident Security Incident Opened 2019-05-24 · Closed 2023-02-22 · 100% similar
GlobalSign: SPKI lacks explicit NULL parameter,
#1575880 RESOLVED Self Reported Incident Revocation Issue Validation Issue Opened 2019-08-22 · Closed 2023-02-22 · 100% similar
GlobalSign: SSL Certificates with US country code and invalid State/Prov
#1579413 RESOLVED Self Reported Incident Opened 2019-09-06 · Closed 2022-11-14 · 100% similar
GlobalSign: OCSP Responder Returns invalid values for Some Precertificates
#1599775 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-11-27 · Closed 2023-02-22 · 100% similar
GlobalSign: Wrong business category (Non Commercial Entity when should have been Private Organization)

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action