Research / Finding
More strict checks in ffmpeg decodiing.
F-TELEGRAM-INTOVF-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
More strict checks in ffmpeg decodiing.
fixed publicly
details
- Finding IDs
- F-TELEGRAM-INTOVF-001
- Status
- fixed publicly
- Reported via
- Telegram security contact
- Note
- public commits eeafe9761409 on 2026-04-07 and 9eda44ca316b on 2026-04-30 add stricter ffmpeg linesize handling, ValidFrameSize checks, max_pixels propagation, and null-allocation failure handling for the reported integer-overflow paths.
F-TELEGRAM-INTOVF-001: Memory safety. Frame size/stride arithmetic is used before bounded frame storage checks. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TELEGRAM-INTOVF-001
Security area (1seal assessment): Memory safety. Frame size/stride arithmetic is used before bounded frame storage checks. 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.