GlobalSign: OV TLS certificate with incorrect countryName value for organization

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 received a Certificate Problem Report on December 2, 2024, regarding an OV TLS certificate that incorrectly listed the countryName as 'US' for an organization based in Turkey. The CA initiated the revocation of the affected certificate and began an investigation into the root cause. The certificate was revoked on December 6, 2024, and an incident report was provided detailing the oversight during the vetting process that allowed the incorrect information to be accepted. GlobalSign has implemented changes to the vetting workflow to prevent similar issues in the future, including requiring explicit approval for changes during certificate renewals and adding a feature for automated cross-checking of address information.

Model: gpt-4o-mini Generated: 2026-06-13 21:37 UTC Revised: 2026-06-16 18:58 UTC Confidence: 0.90 11 comments

Chronology

2024-12-02 GlobalSign received a Certificate Problem Report regarding an OV TLS certificate.
2024-12-06 The affected certificate was revoked.
2025-01-06 GlobalSign completed the implementation of workflow improvements.

Thread Activity

2024-12-03 GlobalSign nv-sa — GlobalSign received a Certificate Problem Report for an OV TLS certificate with an incorrect countryName value.
2024-12-07 GlobalSign nv-sa — The affected certificate has been revoked.
2024-12-09 GlobalSign nv-sa — Incident report detailing the root cause and planned revocations of additional certificates was provided.
2025-01-06 GlobalSign nv-sa — Both updates to the vetting interface and lookup feature have been implemented.

Participants

GlobalSign nv-sa OISTE Mozilla representative

External References

Original Bugzilla Case

Similar Local Cases

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

GlobalSign: Invalid countryName

AI Summary CA Owner

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

GlobalSign: Invalid stateOrProvinceName and locality pair

AI Summary CA Owner

#1866806 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-11-27 · Closed 2024-02-01 · 100% similar

GlobalSign: S/MIME Sponsor validated certificates with CommonName value equal to OrganizationName

AI Summary CA Owner

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

GlobalSign: Incorrect whois information for TLD

AI Summary CA Owner

#1944815 RESOLVED Self Reported Incident Validation Issue Opened 2025-01-30 · Closed 2026-06-10 · 96% similar

GlobalSign: Organization-validated SMIME certificate with invalid organizationIdentifier for European country

AI Summary CA Owner

#1919304 RESOLVED Self Reported Incident Opened 2024-09-17 · Closed 2024-10-23 · 93% similar

GlobalSign: Caching headers inaccurate for subset of CRLs

AI Summary CA Owner

#1714968 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-07 · Closed 2023-02-22 · 90% similar

GlobalSign: Incorrect RegNumber-Org Type combination

AI Summary CA Owner

#1552586 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-05-17 · Closed 2023-02-22 · 89% similar

GlobalSign: 4 Misissued certificates with invalid CN

AI Summary CA Owner