1sealsemantic last-mile verification

Research / Finding

feat: SCTP signaling improvements for reliable connection establishment

F-TELEGRAM-IOS-TGCALLS-SIGNALING-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
TelegramMessenger/tgcallsReported fixTelegramMessenger/tgcalls

feat: SCTP signaling improvements for reliable connection establishment

fixed publicly (upstream tgcalls)
details
Finding IDs
F-TELEGRAM-IOS-TGCALLS-SIGNALING-001
Status
fixed publicly (upstream tgcalls)
Reported via
Telegram security contact
Note
public tgcalls commit 24fd51b on 2026-04-15 adds SCTP signaling reliability fixes, including writable gating and timer backoff bounds. Telegram iOS later pulled a tgcalls submodule revision that includes this fix.

F-TELEGRAM-IOS-TGCALLS-SIGNALING-001: Resource limits. The recorded signaling change bounds timer backoff and gates writes; it is not independent proof of the report-to-fix mapping. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TELEGRAM-IOS-TGCALLS-SIGNALING-001

Security area (1seal assessment): Availability. Bounded retry timing and write gating concern signaling availability; this does not independently confirm the report-to-fix mapping. 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.