← GlobalSign nv-sa cases
Bugzilla #2081595
Ca Certificate Compliance
Incident
Self Reported Incident
Validation Issue
GlobalSign preliminary incident report: EV test certificates missing for two EV-enabled TLS roots
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 opened this bug to disclose that EV test certificates were missing for two of its EV-enabled TLS roots. The initial report says the incident was third-party reported and that GlobalSign was investigating the issue. The bug references the EV Guidelines Appendix A as the relevant policy. GlobalSign said it would provide a full incident report by 2026-10-20. The thread provided does not include any further remediation details or closure.
Chronology
- EV test certificates were found missing for two EV-enabled TLS roots.
Thread Activity
- GlobalSign nv-sa — GlobalSign filed a preliminary incident report stating that EV test certificates were missing for two EV-enabled TLS roots and that the issue was third-party reported.
Participants
GlobalSign nv-sa
External References
Similar Local Cases
GlobalSign: SubCA created with incorrect CPS Policy OID
GlobalSign: Non-BR-Compliant Certificate Issuance -- double-dots in dnsName
GlobalSign: Non-BR-Compliant Certificate Issuance -- RSA key smaller than 2048 bits
GlobalSign: SSL Certificates with US country code and invalid State/Prov
eMudhra emSign PKI Services: TLS certificates missing certificate-type policy OID required by CP/CPS
GlobalSign: Incorrect RegNumber-Org Type combination
GlobalSign: Organization-validated SMIME certificate with invalid organizationIdentifier for European country
GlobalSign: Non-BR-Compliant Certificate Issuance - metadata-only subject fields