check transport progress-token length before allocating the payload buffer
F-TELEGRAM-OOM-001
Portfolio updated: 21 Oct 2026 (the last edit of this record set, not a re-check of every upstream source). Status, releases and attribution belong to each source below; none is inferred from another record.
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.
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.
Paper copy does not update. Current version: 1seal.org/research/findings/F-TELEGRAM-OOM-001/