← GlobalSign nv-sa cases
Bugzilla #1850091 Self Reported Incident

GlobalSign: EV TLS certificate with only metadata in JOI State field

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 that it issued an EV TLS certificate where the jurisdictionStateOrProvinceName field contained only metadata. The issue was triggered by a report received by GlobalSign’s r**********e@globalsign.com email address on 24/08/2023 09:01 UTC, which GlobalSign escalated to its internal SOC and Compliance team. GlobalSign confirmed the certificate in the report required revocation and initiated a revocation and replacement process, including review of outstanding requests and historically issued valid certificates. GlobalSign stated it had no additional historically issued certificates or outstanding requests affected by the issue, and it put vetting management on high-alert with monitoring reports for incoming requests. As remediation, GlobalSign deployed an extended post-issuance linter on 24/08/2023 and later deployed a pre-issuance custom lint on 26/10/2023 to prevent the problem from recurring. The bug was marked RESOLVED with resolution FIXED, and GlobalSign indicated the remedial activities were concluded unless further questions remained.

Model: gpt-5.4-nano Generated: 2026-06-13 21:36 UTC Revised: 2026-06-16 18:57 UTC Confidence: 0.86 5 comments
Chronology
  1. GlobalSign issued the EV TLS certificate later reported as having only metadata in the jurisdictionStateOrProvinceName field.
  2. GlobalSign received a report about the problematic EV TLS certificate and began investigation and revocation/remediation actions.
  3. GlobalSign revoked the affected certificate by 29 August 2023 09:00 UTC at the latest.
  4. GlobalSign deployed a pre-issuance custom lint to check for required unicode character categories.
Thread Activity
  1. GlobalSign nv-sa — Reported steps to reproduce, said GlobalSign was working with the customer to replace the certificate, and stated it would be revoked by 29 August 2023 09:00 UTC at the latest while root-cause analysis proceeded.
  2. GlobalSign nv-sa — Described how GlobalSign became aware (r**********e@globalsign.com), provided a timestamped timeline of escalation, investigation, revocation/replacement initiation, reviews of outstanding and historical certificates, monitoring setup, and linter deployment.
  3. GlobalSign nv-sa — Stated there were no scheduled deliverables that week and that monitoring of new requests continued.
  4. GlobalSign nv-sa — Said pre-issuance lint would be deployed by 29/09/2023 (one week later than initially planned) and that monitoring of new requests continued.
  5. GlobalSign nv-sa — Announced deployment of the pre-issuance custom lint on 26/10/2023 09:20 UTC and stated this concluded the remedial activities unless further questions remained.
Participants
GlobalSign nv-sa
External References
Similar Local Cases
#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
#2034360 RESOLVED Ccadb Metadata Update Self Reported Incident Opened 2026-04-23 · Closed 2026-06-01 · 91% similar
GlobalSign: CRL Distribution Point URLs incomplete for Cross-Certified Root CAs in CCADB records
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 90% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1714968 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2021-06-07 · Closed 2023-02-22 · 90% similar
GlobalSign: Incorrect RegNumber-Org Type combination
#1944815 RESOLVED Self Reported Incident Validation Issue Opened 2025-01-30 · Closed 2026-06-10 · 90% similar
GlobalSign: Organization-validated SMIME certificate with invalid organizationIdentifier for European country
#1658932 RESOLVED Self Reported Incident Opened 2020-08-13 · Closed 2023-02-22 · 90% similar
GlobalSign: Incorrect Jurisdiction of Incorporation information for Japan
#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 88% similar
GlobalSign: Invalid countryName
#1934790 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-12-03 · Closed 2025-01-14 · 88% similar
GlobalSign: OV TLS certificate with incorrect countryName value for organization

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

Confirm action