← SSL.com cases
Bugzilla #2057915 Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Validation Issue

SSL.com preliminary incident report for invalid subject stateOrProvinceName values in 3 OV TLS certificates

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

SSL.com opened a preliminary incident report after receiving a Certificate Problem Report about invalid values in the subject:stateOrProvinceName field for three OV TLS certificates. SSL.com said it was investigating the full root cause and whether any additional certificates were affected. The company stated that the responsible code had been identified and shut off, so no further issuances of this nature should occur. SSL.com also said it would publish a full incident report on or before 2026-08-07. The report cites TLS Baseline Requirements v2.2.8, Section 7.1.2.7.4 as the relevant policy. This case is currently assigned and has not been resolved in the thread provided.

Model: gpt-5.4-mini Generated: 2026-08-04 07:25 UTC Confidence: 0.96 1 comment
Chronology
  1. SSL.com received a Certificate Problem Report about invalid stateOrProvinceName values in 3 OV TLS certificates.
  2. SSL.com identified and shut off the responsible code.
  3. SSL.com said it would post a full incident report by this date.
Thread Activity
  1. SSL.com — SSL.com posted a preliminary incident report, said the issue came from a third-party report, and committed to a full incident report by 2026-08-07.
Participants
SSL.com
External References
Similar Local Cases
#2057919 ASSIGNED Ca Certificate Compliance Problem Reporting Failure Incident Externally Reported Incident Opened 2026-07-26 Still Open · 73% similar
SSL.com: Failure to respond to Certificate Problem Report within 24 hours
#2057448 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Incident Opened 2026-07-24 Still Open · 73% similar
SwissSign: Invalid Entry in State field
#1705647 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-04-16 · Closed 2023-02-22 · 72% similar
KIR S.A.: Invalid organizationName
#2058918 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Revocation Issue Opened 2026-07-29 Still Open · 71% similar
CFCA: Incorrect countryName values in OV subscriber certificates
#1586604 RESOLVED Certificate Misissuance Validation Issue Opened 2019-10-06 · Closed 2022-11-14 · 71% similar
DigiCert: TERENA: No localityName in EV precert
#1759122 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2022-03-11 · Closed 2022-11-14 · 71% similar
DigiCert: EV for Onion addresses without Tor Service Descriptor
#1398246 RESOLVED Ca Certificate Compliance Incident Opened 2017-09-08 · Closed 2023-02-22 · 71% similar
Consorci AOC: Non-BR-Compliant OCSP Responders
#1398428 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2017-09-09 · Closed 2023-02-22 · 71% similar
Amazon Trust Services: CAA Misissuances

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

Confirm action