← GlobalSign nv-sa cases
Bugzilla #2007098 Repository Issue

GlobalSign: CCADB CRL URL mismatch with issued certificate CDP for EV CA (SHA256-G3)

RESOLVED FIXED 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

This case reports a CCADB compliance issue for GlobalSign Extended Validation CA - SHA256 - G3, where the CCADB “Full CRL Issued By This CA” entry used a CRL URL without an extra “/gs/”, while the issued certificates’ CDP contained an extra “/gs/” in the qualifier. The thread states that both URLs locate to the same CRL, but the CCADB URL did not match exactly the CRL URL as it appears in the issued certificates, contrary to CCADB Policy section 6.2. The issue was disclosed via a third-party certificate problem report received on 18/12/2025, and GlobalSign investigated the CCADB record. GlobalSign corrected the CCADB CRL value on 19/12/2025 to align with the CDP from the issued certificates and confirmed no other CA records were affected. GlobalSign also updated its CCADB management procedure to require analysis of production configuration in addition to internal documentation review and added an automated profile check to verify CRL URLs of issued certificates against CCADB records. The thread indicates the remedial activities were completed on 28/01/2026 and GlobalSign requested closure; the bug is currently RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:38 UTC Revised: 2026-06-16 18:58 UTC Confidence: 0.90 8 comments
Chronology
  1. Non-compliance period begins for the affected CCADB/issued-certificate CRL URL alignment.
  2. GlobalSign receives a third-party certificate problem report about a potential CCADB vs issued-certificate CDP inconsistency.
  3. GlobalSign confirms the CCADB record issue and corrects the CCADB CRL URL to match the issued certificates’ CDP.
  4. GlobalSign completes implementation of an automated profile check to verify CRL URLs against CCADB records.
  5. GlobalSign posts the incident report closure summary and requests closure.
  6. Bug is set to RESOLVED (FIXED).
Thread Activity
  1. GlobalSign nv-sa — GlobalSign provides a preliminary incident report describing the CCADB CRL URL mismatch (missing “/gs/” vs issued-certificate CDP) and states it updated the CCADB entry and is investigating.
  2. GlobalSign nv-sa — GlobalSign posts a full incident report with timeline, states issuance was not stopped because both URLs point to the correct CRL, and lists corrective actions taken (including correcting the CCADB value).
  3. GlobalSign nv-sa — GlobalSign reports completion of an action item updating the CCADB management procedure to analyze production configuration in addition to internal documentation review.
  4. GlobalSign nv-sa — GlobalSign states it is on track to implement an automated profile check to verify CRL URLs by January 30, 2026.
  5. GlobalSign nv-sa — GlobalSign repeats it is on track for the automated profile check implementation by January 30, 2026.
  6. GlobalSign nv-sa — GlobalSign states the automated profile check was completed on January 28, 2026, and that it will post a closure report by February 5, 2026.
  7. GlobalSign nv-sa — GlobalSign posts the closure summary, describing the root cause and remediation (procedure update, corrected internal documentation, and automated profile check) and requests closure.
  8. CCADB representative — CCADB incident reporting requests final comments and states the incident will be closed approximately 2026-02-12.
Participants
GlobalSign nv-sa CCADB representative
Similar Local Cases
#1829195 RESOLVED Common Ca Database Repository Issue Opened 2023-04-20 · Closed 2023-05-04 · 87% similar
GlobalSign: CRLs reported in CCADB unavailable
#2007066 RESOLVED Ccadb Metadata Update Repository Issue Opened 2025-12-19 · Closed 2026-01-20 · 70% similar
Disig: Missing CA Disig R2I2 Certification Service Full CRL URLs in CCADB
#2012934 RESOLVED Ccadb Metadata Update Repository Issue Opened 2026-01-28 · Closed 2026-02-26 · 69% similar
Telia: Inccorrect CRL URL on a Root CA record in CCADB
#2047866 RESOLVED Ccadb Metadata Update Ccadb Disclosure Issue Remediation Tracking Opened By Ca Opened 2026-06-16 · Closed 2026-07-21 · 67% similar
certSIGN: incorrect URL in CCADB
#2007238 RESOLVED Ca Documents Repository Issue Opened 2025-12-20 · Closed 2026-01-12 · 67% similar
Certigna: CRL URL Disclosure
#2049012 ASSIGNED Ccadb Metadata Update Incident Ccadb Disclosure Issue Policy Document Issue Opened 2026-06-19 Still Open · 60% similar
FNMT: Inaccuracy in CRL URL in CCADB
#2054450 UNCONFIRMED Common Ca Database Ccadb Disclosure Issue Incident Externally Reported Incident Opened 2026-07-13 Still Open · 59% similar
Firmaprofesional: Chrome Root Program Policy - Incorrect CCADB hierarchy associations
#2050850 ASSIGNED Ca Certificate Compliance Common Ca Database Ccadb Disclosure Issue Policy Document Issue Opened 2026-06-26 Still Open · 59% similar
Asseco DS / Certum: HTTP 404 returned by CRL Distribution Point URLs for six pre-inclusion Root CAs

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

Confirm action