← Deutsche Telekom Security GmbH cases
Bugzilla #2076163 Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Remediation Tracking

Telekom Security delayed response to a Certificate Problem Report within 24 hours

ASSIGNED Deutsche Telekom Security GmbH
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

Deutsche Telekom Security GmbH reported that it received a Certificate Problem Report on Saturday, 2026-09-26, but did not respond until Monday morning. The bug is explicitly about the failure to provide first feedback within the 24-hour deadline in CA/B Forum Baseline Requirements Section 4.9.5. Telekom stated that this incident was self-reported and that it was not related to bug 2076096. The full incident report says the non-compliance began at 2026-09-27 16:24 UTC and ended at 2026-09-28 07:13 UTC, when the first email was sent to the reporter. Telekom also noted that the certificates mentioned in the problem report were revoked within the required timeframe, and that this bug concerns only the delayed response, not the underlying certificate issue. The bug remains assigned, and a later comment says the team is working on an open action item and requested the next update date be set to 2026-10-30.

Model: gpt-5.4-mini Generated: 2026-10-20 17:37 UTC Confidence: 0.99 3 comments
Chronology
  1. Telekom received a Certificate Problem Report.
  2. The 24-hour deadline for first feedback to the reporter passed without a response.
  3. Telekom sent the first email response to the problem reporter.
  4. All certificates affected by the problem report were revoked.
Thread Activity
  1. Telekom representative — Telekom filed a preliminary incident report saying it received a Certificate Problem Report on 2026-09-26 but did not address it until the following Monday morning, and identified BR Section 4.9.5 as the relevant policy.
  2. Telekom representative — Telekom filed the full incident report with the UTC timeline, confirmed the non-compliance window, and said the bug is about delayed response rather than the revocation issue described in the report.
  3. Telekom representative — Telekom said it is working on the open action item and requested the Next Update field be set to 2026-10-30.
Participants
Telekom representative
Similar Local Cases
#2077068 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Opened 2026-10-01 Still Open · 100% similar
Telekom Security: Failure in automatic issuance of CRLs
#2083715 NEW Ca Certificate Compliance Incident Externally Reported Incident Policy Document Issue Opened 2026-10-19 Still Open · 88% similar
Telekom Security / DFN: CRL validity period exceeds 10 days by one second
#2076096 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Repository Issue Opened 2026-09-28 Still Open · 87% similar
Telekom Security / DFN: crlEntryExtensions SEQUENCE of size 0
#2080708 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Vulnerability Disclosure Opened 2026-10-12 Still Open · 77% similar
Telekom Security: OCSP responder uses incorrect signature algorithm for P-384 signing key
#1877388 RESOLVED Delayed Revocation Incident Self Reported Incident Opened 2024-01-30 · Closed 2025-03-14 · 76% similar
Telekom Security: Revocation delay for TLS certificates with basicConstraints not marked as critical
#1875820 RESOLVED Incident Certificate Misissuance Self Reported Incident Opened 2024-01-22 · Closed 2024-08-03 · 76% similar
Telekom Security: TLS certificates with basicConstraints not marked as critical
#2084213 UNCONFIRMED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-10-20 Still Open · 75% similar
SwissSign: Delayed Response to CPR - Bugzilla 2083791
#2083693 UNCONFIRMED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-10-19 Still Open · 75% similar
Asseco DS / Certum: Delayed preliminary CPR response due to email address typo

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

⚠

Confirm action