Research / Finding
Non-Constant-Time Message Key Comparison in Secret Chat Decryption Violates Security Guidelines
F-TELEGRAM-E2E-001
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
Non-Constant-Time Message Key Comparison in Secret Chat Decryption Violates Security Guidelines
fixed publicly
details
- Finding IDs
- F-TELEGRAM-E2E-001
- Status
- fixed publicly
- Reported via
- Telegram security contact
- Note
- accepted as LOW. public fix commit 9d33962c013e68dcecd8c26bb23ca232bc52c2a2 on 2026-02-13 replaces direct message-key comparison with constTimeIsEqual; the fix is present in release-12.5.
F-TELEGRAM-E2E-001: Secret handling. Message-key comparison is not constant-time. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TELEGRAM-E2E-001
Security area (1seal assessment): Confidentiality. Message-key comparison is not constant-time. Reviewed 24 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.