Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Telegram-0-Click-RCE-SECURITY-VULNERABILITY-ANALYSIS-REPORT — I have submitted a report on the Telegram sticker vulnerability, SECURITY VULNERABILITY ANALYSIS REPORT Telegram 0-Click RCE vulnerability ZDI-CAN-30207 | CVSS 9.8 CRITICAL. | Kitploit
Tools/GitHubGitHub/gameworkerkim/telegram-0-click-rce-security-vulnerability-analysis-report
Android SecurityVulnerability AnalysisExploitationMobile SecurityThreat IntelligencePapers & ResearchIncident Response
GitHubgameworkerkim/telegram-0-click-rce-security-vulnerability-analysis-report

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Telegram-0-Click-RCE-SECURITY-VULNERABILITY-ANALYSIS-REPORT

I have submitted a report on the Telegram sticker vulnerability, SECURITY VULNERABILITY ANALYSIS REPORT Telegram 0-Click RCE vulnerability ZDI-CAN-30207 | CVSS 9.8 CRITICAL.

View Repository
2117 months agoNot yet reviewed

🔴 Telegram 0-Click RCE Vulnerability Analysis Report

ZDI-CAN-30207 | CVSS 9.8 CRITICAL | Unpatched (as of 2026-03-30)

Author: Dennis Kim (@gameworkerkim)
Date: March 30, 2026
Contact: [email protected]


📋 Summary Badges

CVSS Status Platform PoC Disclosure


1. Vulnerability Overview (Executive Summary)

This is a zero-click remote code execution (RCE) vulnerability in the Telegram Android/Linux platforms, for which CSIRT Italy of the Italian National Cybersecurity Agency (ACN) issued an official alert in late March 2026. It was discovered by researcher Michael DePlante (@izobashi) of Trend Micro's Zero Day Initiative (ZDI) and assigned the internal identifier ZDI-CAN-30207.

This vulnerability allows an attacker to execute arbitrary code on the victim's device simply by sending a crafted animated sticker or media file to the victim. No action by the user (clicking, accepting a download, etc.) is required, making it one of the most dangerous vulnerability types in the messenger security field.

Note Telegram's official feedback: it's fake, no real vulnerability is reported

Key Information

ItemDetails
Vulnerability IdentifierZDI-CAN-30207 (No CVE assigned)
CVSS v3.1 Score9.8 / 10 (Critical)
CVSS VectorAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability TypeZero-Click Remote Code Execution (RCE)
DiscovererMichael DePlante (@izobashi) / Trend Micro ZDI
Affected PlatformsTelegram Android, Telegram Linux
Telegram Notification DateMarch 26, 2026
Scheduled Disclosure DateJuly 24, 2026 (ZDI standard 90-120 day policy)
Patch Status⚠️ Unpatched (No official patch as of 2026-03-30)
PoC DisclosureNot disclosed (Private exploit may exist)
Confirmed In-the-Wild ExploitationUnconfirmed (No confirmed in-the-wild exploitation)
CSIRT AlertOfficial alert issued by CSIRT Italy (ACN)

2. Technical Analysis

2.1 Attack Vector and Mechanism

The core of the attack lies in the process by which Telegram automatically generates previews for received media files (especially animated stickers). During this parsing stage, a crafted file triggers a vulnerable code path that leads to RCE.

공격 흐름:
1. 공격자 → 피해자에게 조작된 애니메이션 스티커/미디어 파일 전송
2. Telegram 앱이 메시지 수신 즉시 자동으로 미리보기 생성을 위한 파싱 시작
3. 파싱 과정에서 조작된 데이터가 취약점을 트리거 → 메모리 오염 또는 타입 혼동 발생
4. 공격자의 코드가 Telegram 프로세스 권한으로 실행됨

2.2 CVSS v3.1 Detailed Analysis

MetricValueMeaning
Attack Vector (AV)NetworkRemotely exploitable over the internet
Attack Complexity (AC)LowNo special conditions or complex bypass techniques required
Privileges Required (PR)NoneNo attacker account or special privileges required
User Interaction (UI)NoneNo action by the victim required (Zero-Click)
Scope (S)UnchangedImpact confined within the vulnerable component
Confidentiality (C)HighFull compromise of confidentiality including messages, sessions, and media
Integrity (I)HighSystem files and data can be tampered with
Availability (A)HighService disruption and compromise of device availability

2.3 Comparison with Similar Past Vulnerabilities — rlottie Library Analysis

Telegram's rlottie library (an animated sticker rendering engine) has a history of numerous similar vulnerabilities (Heap Buffer Overflow, Stack Overflow, Type Confusion) discovered in its Android/iOS/macOS versions by the Shielder research team in 2021. Those vulnerabilities required minimal user interaction, but ZDI-CAN-30207 is far more severe in that it achieves a complete zero-click.

Telegram rlottie GitHub
⚠️ Most commits are from 7 years ago, indicating an absence of ongoing maintenance.

rlottie was developed in C++14, and due to the nature of modern C++, its high level of abstraction makes debugging difficult. The fact that most commits in the GitHub source code date back 7 years suggests that the lack of continuous maintenance is not unrelated to the emergence of this vulnerability.


3. Threat Assessment

3.1 Scope of Impact

Telegram has over 1 billion active users worldwide.

CategoryDetails
Confirmed affected platformsTelegram for Android, Telegram for Linux
Potential impact unconfirmediOS, Windows, macOS versions
Affected targetsAll users who receive messages from unspecified senders via Telegram

3.2 Threat Actor Analysis

A complete zero-click RCE vulnerability with a CVSS score of 9.8 has historically been a prime target for state-sponsored cyber attack groups (APTs) and commercial spyware developers (such as NSO Group).

  • 🔴 State-level cyber espionage activities (targeting journalists, politicians, and activists)
  • 🔴 Limited exploitation after prior acquisition through private submission to ZDI
  • 🔴 Trading of vulnerability information on the dark web (sale listings spotted in the Russian security community)
  • 🔴 Potential strategic use by APT groups during the pre-patch window

3.3 Limitations of Disabling Auto-Download

⚠️ Important: Disabling auto-download does not block this vulnerability.

The vulnerability is triggered not at the file execution stage after download completes, but at the preview parsing stage that occurs automatically upon message receipt. Disabling auto-download in settings does not constitute an effective mitigation.


4. Telegram's Response Status

To date, Telegram's official side has maintained a highly unusual silence. ZDI notified Telegram of the vulnerability on March 26, 2026, and in accordance with standard Responsible Disclosure procedures, set July 24, 2026 as the disclosure deadline.

A Telegram spokesperson denied the existence of this vulnerability, but this contradicts the official alerts from ZDI and CSIRT Italy, and industry experts have expressed strong doubts about Telegram's claims.

ItemStatus
Telegram NotificationMarch 26, 2026
Telegram Official PatchNot Released
ZDI Disclosure ScheduledJuly 24, 2026 (Full technical details disclosed if patch incomplete)
CSIRT Italy AlertIssued (Official analysis and mitigation guide provided)
Telegram Official PositionDenies existence of vulnerability (Industry experts refuting)

5. 완화 방안 및 권고사항 (Mitigation & Recommendations)

5.1 Immediate Actions

  • ❗ High-risk users (journalists, politicians, executives, security personnel) should refrain from using the native Telegram (Android/Linux) app until an official patch is released
  • ✅ Where possible, use Telegram Web (web version) in the latest browser as an alternative
  • ✅ In Telegram privacy settings, restrict receipt of messages from 'unknown people' (including group invitations)
  • ✅ Monitor Telegram emergency security updates through official channels
  • ✅ Treat all received media and stickers as potential threats

5.2 Organization-Level Recommendations

Download Tool