General: Better validation for iframe event origins (#6856)

F-WEBA-POSTMSG-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

Ajaxy/telegram-ttReported fixAjaxy/telegram-tt

General: Better validation for iframe event origins (#6856)

partially likely fixed publicly (re-test needed)

details

Finding IDs: F-WEBA-POSTMSG-001
Status: partially likely fixed publicly (re-test needed)
Reported via: Telegram security contact
Note: public WebA commit 7e789e6 on 2026-04-17 adds isMessageFromIframe(...) checks so iframe events are accepted only from the expected iframe. caveat: outbound postMessage(..., '*') patterns may still exist, so this is tracked as partial/likely fixed pending re-test if the original issue was specifically targetOrigin='*'.

F-WEBA-POSTMSG-001: Access control. Incoming iframe messages require source/origin binding; outbound targetOrigin coverage remains unconfirmed. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-WEBA-POSTMSG-001

Security area (1seal assessment): Authorization. Incoming iframe events are bound to the intended source, restricting who can invoke the message handler. This does not establish coverage of outbound targetOrigin behavior. 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.