LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47793: Telegram Desktop 2.9.2 - Denial of Service (PoC)

Telegram Desktop 2.9.2 contains a denial of service vulnerability that allows attackers to crash the application by sending an oversized message payload. Attackers can generate a 9 million byte buffer and paste it into the messaging interface to trigger an application crash.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-47793 is a denial-of-service issue in Telegram Desktop 2.9.2. A specially oversized message can crash the desktop application. This affects availability of the client, not confidentiality or integrity based on the provided CVSS data. Public proof-of-concept material exists, but the sources do not show active exploitation.

Executive priority

Prioritize remediation where Telegram Desktop is business-critical or broadly deployed. This is not a data-theft issue based on current sources, but it can disrupt user communications. Address through endpoint software governance and version control rather than emergency incident response unless crashes are observed.

Technical view

Telegram Desktop 2.9.2 is reported vulnerable to resource-consumption denial of service, mapped to CWE-770. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5. The described trigger is an oversized message payload causing application crash. No affected versions beyond 2.9.2 are identified in the supplied sources.

Likely exposure

Exposure is limited to environments running Telegram Desktop 2.9.2. The impact is application availability: users may lose access to the desktop client until it is restarted or otherwise recovered. Server-side Telegram services and other Telegram products are not identified as affected in the provided sources.

Exploitation context

A public ExploitDB entry and VulnCheck advisory describe proof-of-concept conditions. The CVE is not listed as CISA KEV in the supplied data, and no cited source states active exploitation. Treat this as a known public DoS technique, not confirmed in-the-wild exploitation.

Researcher notes

The record’s key evidence is third-party advisory and ExploitDB PoC references. The CVE was published in 2026 for a Telegram Desktop 2.9.2 issue titled from 2021. Sources do not identify a vendor advisory, fixed version, or broader affected range, so validation should avoid assuming impact beyond 2.9.2.

Mitigation direction

  • Inventory endpoints for Telegram Desktop 2.9.2.
  • Check Telegram guidance and release notes for fixed or current versions.
  • Upgrade away from version 2.9.2 where business use requires Telegram Desktop.
  • Restrict or remove unauthorized Telegram Desktop installations if not business-approved.

Validation and detection

  • Confirm installed Telegram Desktop versions through endpoint inventory.
  • Review application crash logs for Telegram Desktop availability incidents.
  • Verify users no longer run version 2.9.2 after remediation.
  • Track vendor or advisory updates for affected-version clarification.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47793 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-47793Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TelegramTelegram Desktop2.9.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.