1sealsemantic last-mile verification

Research / Finding

update to 12.6.2 (6655)

F-TGAND-SECRETCHAT-VECTOR-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
DrKLO/TelegramReported fixDrKLO/Telegram

update to 12.6.2 (6655)

fixed publicly
details
Finding IDs
F-TGAND-SECRETCHAT-VECTOR-001
Status
fixed publicly
Reported via
Telegram security contact
Note
public android commit fb98f157afb3 on 2026-04-05 (12.6.2) adds validateSize(...) checks in the affected Vector.java path and appears to close the reported secret-chat vector-size issue.

F-TGAND-SECRETCHAT-VECTOR-001: Input / state handling. Vector-size validation is added at the secret-chat decoding boundary. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TGAND-SECRETCHAT-VECTOR-001

Security area (1seal assessment): Availability. Rejecting invalid vector sizes prevents malformed secret-chat input from reaching excessive allocation or parser failure; native memory corruption is not established here. 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.