← SSL.com cases
Bugzilla #2057915 Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Validation Issue Problem Reporting Failure

SSL.com third-party incident report for invalid subject stateOrProvince values; all action items completed

ASSIGNED SSL.com
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

This case remains a third-party Certificate Problem Report about invalid subject stateOrProvinceName values in SSL.com certificates. SSL.com said a business-registry lookup tool used during organization validation could auto-fill subject fields in the background and, in some cases, insert malformed geographic information or contribute to an organization-name mismatch. SSL.com reported that the feature was turned off during investigation and that all 20 affected certificates are now revoked. The company also stated that there was no revocation delay. In the latest update, SSL.com said Action Item #5, its internal response rework for potential misissuance events, was completed on 2026-10-29, and that all action items for the incident are now complete. SSL.com said it plans to provide a Report Closure Summary on or before 2026-11-06 if there are no further comments or questions.

Model: gpt-5.4-mini Generated: 2026-08-04 07:25 UTC Revised: 2026-11-01 07:00 UTC Confidence: 0.97 10 comments
Chronology
  1. A business-registry lookup tool began auto-filling subject fields during organization validation.
  2. A third-party Certificate Problem Report was received about invalid stateOrProvinceName values in OV TLS certificates.
  3. The business-registry lookup feature was turned off.
  4. SSL.com reported 20 affected certificates and said 15 were revoked at that time.
  5. SSL.com updated the incident report and said all 20 affected certificates were identified.
  6. SSL.com said Action Item #3 had begun deployment in staging and Action Item #4 had been deployed to production.
  7. SSL.com said Action Item #3 was complete and Action Item #5 remained in progress.
  8. SSL.com said leadership approved its updated internal response to potential misissuance events, completing Action Item #5.
Thread Activity
  1. SSL.com — SSL.com posted a preliminary incident report saying it had received a third-party CPR and was investigating the root cause and scope.
  2. SSL.com — SSL.com said it was concluding its investigation and preparing the full incident report within the 14-day timeframe.
  3. SSL.com — SSL.com posted the full incident report describing the business-registry lookup tool, the affected certificate counts, and the revocation status at that time.
  4. SSL.com — SSL.com reposted the report with updates, said it found 20 total affected certificates, and said it would continue monitoring the bug and provide another update by 2026-08-21.
  5. SSL.com — SSL.com said it continues to monitor the bug, work on the action items, and will provide an update on or before 2026-08-28.
  6. SSL.com — SSL.com said development and code review for Action Items #3 and #4 were complete, both changes were merged, production deployment was scheduled, and Action Item #5 remained in progress.
  7. SSL.com — SSL.com said Action Item #3 had begun deployment in staging, Action Item #4 was deployed to production, Action Item #5 remained in progress, and the business-registry lookup would stay disabled until completion.
  8. SSL.com — SSL.com said Action Item #3 was deployed and complete, while Action Item #5 remained in progress.
  9. SSL.com — SSL.com said Action Item #5 was complete, all action items were finished, and it planned to provide a closure summary by 2026-11-06.
Participants
SSL.com
External References
Similar Local Cases
#2065634 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Revocation Issue Opened 2026-08-21 Still Open · 96% similar
SSL.com: Invalid combinations of countryName, stateOrProvinceName, and localityName attributes
#2057318 RESOLVED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Revocation Issue Opened 2026-07-23 · Closed 2026-09-14 · 73% similar
GlobalSign: Unicode replacement character issue in Subject
#2065895 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Problem Reporting Failure Opened 2026-08-23 Still Open · 72% similar
GlobalSign: StateOrProvince and LocalityName value inconsistency
#2047843 RESOLVED Ca Certificate Compliance Problem Reporting Failure Revocation Issue Opened 2026-06-16 · Closed 2026-07-09 · 72% similar
Certigna: Pre-certificates not recognised by the OCSP responder
#2080806 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Opened 2026-10-12 Still Open · 71% similar
Actalis: Non-compliant OCSP responses and OCSP responder certificate
#2069766 RESOLVED Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure Opened 2026-09-06 · Closed 2026-09-22 · 71% similar
DigiCert: CPR subject.countryName
#2077538 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-10-02 Still Open · 71% similar
Sectigo: Certificates issued for sanctioned entities
#2070071 RESOLVED Ca Certificate Compliance Externally Reported Incident Incident Self Reported Incident Opened 2026-09-08 · Closed 2026-10-02 · 71% similar
Sectigo: Issuance of certificates including a Subject:countryName not corresponding to a Country

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

⚠

Confirm action