{"uuid": "3b113bca-657a-49f5-9f35-42ba8e999d7b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-107181", "type": "seen", "source": "https://t.me/tginfoen/2201", "content": "Dangerous vulnerability in Telegram Desktop: any file can be stolen with one click\n\nWhat you MUST NOT do and how to protect yourself:\n\u2022 Do not keep using versions earlier than 7.2.9 \u2014 update the client immediately. If you use an unofficial client, temporarily switch to the official one until an update is released.\n\nDownload:\n \u2022 Windows / macOS / Linux: official website or GitHub.\n \u2022 Windows: Microsoft Store.\n \u2022 macOS: App Store.\n \u2022 Linux: Flathub, Snapcraft.\n\nAdvice for users of older clients:\n\n\u2022 Links can be dangerous: whenever you click a link, read the pop-up window carefully \u2014 if Telegram shows an unusual structure in the link (for example, one starting with tg://), do not open it.\n\n\u2022 Do not use the client without a local passcode: enabling one encrypts the session files in the tdata directory, preventing immediate account hijacking even if those files are leaked.\n\nWhat is the issue?\n\nA vulnerability has been discovered in Telegram Desktop clients earlier than version 7.2.9 (CVE-2026-107181). Because the ; delimiter was not escaped, parameters in tg:// links were interpreted as separate IPC commands. Using the interpret: handler, an attacker could cause files from the system to be sent covertly to their channel, without the user\u2019s confirmation, when the user clicked a specially crafted link.\n\nThe main risk\n\nThe danger is not limited to stealing tdata session files and hijacking accounts. Exploiting the vulnerability makes it possible to covertly steal absolutely any files on the computer that the user can access: documents, saved browser sessions, SSH keys, system configurations, or cryptocurrency wallets.\n\n#security #desktop #vulnerabilities", "creation_timestamp": "2026-10-09T09:42:04.000000Z"}