← GlobalSign nv-sa cases
Bugzilla #2057318 Self Reported Incident Certificate Misissuance Validation Issue

GlobalSign self-reported incident: Unicode replacement character in TLS certificate subject, remediation completed

ASSIGNED 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 single TLS end-entity certificate incident involving a Unicode replacement character (U+FFFD) in the Subject distinguished name stateOrProvinceName field. The case was triggered by a third-party Certificate Problem Report, after which GlobalSign investigated and filed a preliminary report, then a full incident report. GlobalSign said the certificate was issued with malformed subject encoding due to incorrect TeletexString-to-UTF-8 handling during issuance, and that the affected certificate has since been revoked. The report states that issuance was not stopped, but requests were monitored for recurrence and the ftfy module was enabled as a backup measure. In the latest update, GlobalSign said it enabled ftfy in pkimetal on 2026-08-24, completed review of active modules on 2026-08-27, and that this concludes the identified remedial activities; it said it will post a closure report by 2026-09-03.

Model: gpt-5.4-mini Generated: 2026-07-26 06:23 UTC Revised: 2026-08-30 06:02 UTC Confidence: 0.98 7 comments
Chronology
  1. A TLS end-entity certificate was issued with malformed Subject encoding.
  2. A Certificate Problem Report identified a Unicode replacement character issue in the certificate subject.
  3. The affected certificate was revoked.
  4. ftfy was enabled in pkimetal on the Atlas platform.
  5. GlobalSign completed review of active modules in pkimetal for both platforms.
Thread Activity
  1. GlobalSign nv-sa — GlobalSign said it had received a CPR, was investigating, and would provide a full incident report by 2026-07-30.
  2. GlobalSign nv-sa — GlobalSign posted the full incident report describing the malformed subject encoding, the revocation of the affected certificate, and the code fix and ftfy enablement.
  3. GlobalSign nv-sa — GlobalSign said it was on track to enable ftfy in pkimetal by 2026-08-27 and requested the next update be set for 2026-08-28.
  4. GlobalSign nv-sa — GlobalSign repeated that it is on track to enable ftfy in pkimetal by 2026-08-27 and requested the next update be set for 2026-08-28.
  5. GlobalSign nv-sa — GlobalSign said ftfy had been enabled in pkimetal on 2026-08-24 and that it was on track with the remaining action.
  6. GlobalSign nv-sa — GlobalSign said the review of active modules in pkimetal for both platforms was completed on 2026-08-27 and that it would post a closure report by 2026-09-03.
Participants
GlobalSign nv-sa
External References
Similar Local Cases
#2058503 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-07-28 · Closed 2026-09-02 · 90% similar
GlobalSign: SubCA created with incorrect CPS Policy OID
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 81% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1944815 RESOLVED Self Reported Incident Validation Issue Opened 2025-01-30 · Closed 2026-06-10 · 81% similar
GlobalSign: Organization-validated SMIME certificate with invalid organizationIdentifier for European country
#1866806 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-11-27 · Closed 2024-02-01 · 80% similar
GlobalSign: S/MIME Sponsor validated certificates with CommonName value equal to OrganizationName
#1575880 RESOLVED Self Reported Incident Revocation Issue Validation Issue Opened 2019-08-22 · Closed 2023-02-22 · 80% similar
GlobalSign: SSL Certificates with US country code and invalid State/Prov
#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 79% similar
GlobalSign: Invalid countryName
#1934790 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-12-03 · Closed 2025-01-14 · 79% similar
GlobalSign: OV TLS certificate with incorrect countryName value for organization
#1552586 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-05-17 · Closed 2023-02-22 · 79% similar
GlobalSign: 4 Misissued certificates with invalid CN

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

Confirm action