← GlobalSign nv-sa cases
Bugzilla #2057318
Ca Certificate Compliance
Incident
Certificate Misissuance
Problem Reporting Failure
Opened By Ca
GlobalSign preliminary incident report for Unicode replacement character issue in certificate subject
UNCONFIRMED
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 case after receiving a Certificate Problem Report about a Unicode replacement character issue in the Subject of one end-entity certificate. The initial comment says GlobalSign is investigating the issue and will provide a full incident report by 2026-07-30. The report cites RFC 5280 Section 4.1.2.6 as the relevant policy. The thread does not state any remediation or final resolution yet. It also explicitly says the source of the incident disclosure was a third-party report.
Chronology
- A Certificate Problem Report was received about a Unicode replacement character issue in the Subject of one end-entity certificate.
Thread Activity
- GlobalSign nv-sa — GlobalSign said it had received a CPR, was investigating, and would provide a full incident report by 2026-07-30.
Participants
GlobalSign nv-sa
External References
Similar Local Cases
GlobalSign: Non-BR-Compliant Certificate Issuance - metadata-only subject fields
eMudhra emSign PKI Services: Invalid Subject Locality/State Values
Verify GlobalSign's continued conformance to EV guidelines
Actalis: Undisclosed Subordinate CA Certificate
Izenpe: Multiple invalid EV certificates issued
Microsoft PKI Services: Improper Disclosure of CRLs – Does Not Match CA Subject
Microsoft PKI Services: Policy document bug
D-TRUST: Certificate with RSA key where modulus is not divisible by 8