1sealsemantic last-mile verification

Research / Finding

check transport progress-token length before allocating the payload buffer

F-TELEGRAM-OOM-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/Telegram-iOSReported fixTelegramMessenger/Telegram-iOS

check transport progress-token length before allocating the payload buffer

partially fixed publicly
details
Finding IDs
F-TELEGRAM-OOM-001
Status
partially fixed publicly
Disclosure date
Note
transportDecodeProgressToken checks data.length before subtracting 24. This matches the primary underflow vector; it does not establish fixes for every accompanying MTInputStream short-read case. The full report and release rollout were not independently retested.

F-TELEGRAM-OOM-001: Resource limits. Token-length underflow leads to an oversized allocation. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TELEGRAM-OOM-001

Security area (1seal assessment): Availability. Length underflow on a short input can request an excessive allocation. Reviewed 23 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.