Research / Finding
restrict tg://iv decode to safe links
F-TELEGRAM-WEBK-TGIV-DECODE-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.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
restrict tg://iv decode to safe links
fixed publicly
details
- Finding IDs
- F-TELEGRAM-WEBK-TGIV-DECODE-001
- Status
- fixed publicly
- Reported via
- Telegram security contact
- Note
- public WebK/tweb commit 6af7087389c0 restricts tg://iv local decode handling to safe links; unsafe or broken links no longer keep the local handler.
F-TELEGRAM-WEBK-TGIV-DECODE-001: Input / state handling. Unsafe or malformed links reach the local tg://iv decoding handler. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TELEGRAM-WEBK-TGIV-DECODE-001
Security area (1seal assessment): Semantics. The tg://iv decoder distinguishes trusted link data from unsafe input before enabling local URL handling. Reviewed 21 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.
Paper copy does not update. Current version: 1seal.org/research/findings/F-TELEGRAM-WEBK-TGIV-DECODE-001/