More strict checks in ffmpeg decodiing.

F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

telegramdesktop/tdesktopReported fixtelegramdesktop/tdesktop

More strict checks in ffmpeg decodiing.

fixed publicly

details

Finding IDs: F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001
Status: fixed publicly
Reported via: Telegram security contact
Note: public commit eeafe9761409 on 2026-04-07 adds decoded frame area guards; follow-up commit 9eda44ca316b on 2026-04-30 strengthens frame-size validation with ValidFrameSize and max_pixels handling for the same ffmpeg frame-size class.

F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001: Resource limits. Decoded frame area needs a limit before allocating frame storage. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001

Security area (1seal assessment): Availability. The decoded frame-area guard bounds frame storage allocation, protecting decoder availability; this record does not independently establish memory corruption. 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.