Security readout for executives and security teams
Plain-English summary
Telegram Desktop 0.10.19 created its local data directory with permissions that could let other local users read sensitive authentication information. The business risk is account/session exposure on shared or multi-user systems, not a remote internet-facing compromise based on the provided sources.
Executive priority
Prioritize where Telegram Desktop runs on shared workstations, jump hosts, or any endpoint with multiple local users. Single-user endpoints are lower urgency, but exposed authentication data can still justify session review.
Technical view
The CVE describes insecure filesystem permissions: $HOME/.TelegramDesktop was created with mode 0755, allowing local users to access sensitive authentication information through normal filesystem access. The source bundle cites a Telegram Desktop GitHub issue and a confirming commit, but provides no CVSS score, CWE mapping, or release-level fix guidance.
Likely exposure
Exposure is most plausible on Unix-like shared endpoints or servers where Telegram Desktop 0.10.19 is installed and local users have accounts on the same host.
Exploitation context
The provided sources do not show active exploitation, and CISA KEV status is false. Exploitation requires local user access to the same system and relies on overly permissive directory permissions, not a remote network vector.
Researcher notes
Evidence is limited to the CVE description, GitHub issue, and a confirming commit. The bundle does not provide affected platform detail, CVSS, exploit reports, or exact fixed release mapping, so validation should stay focused on version and filesystem permissions.
Mitigation direction
- Check Telegram Desktop vendor guidance for the fixed release containing the referenced commit.
- Upgrade Telegram Desktop where a fixed vendor-supported build is available.
- Restrict $HOME/.TelegramDesktop so only the owning user can read it.
- Review local account access on affected multi-user systems.
- Revoke or refresh Telegram sessions if local exposure is suspected.
Validation and detection
- Inventory systems for Telegram Desktop 0.10.19 installations.
- Check ownership and permissions on each user's $HOME/.TelegramDesktop directory.
- Confirm other local users cannot read the directory contents.
- Verify upgraded builds no longer create the directory with 0755 permissions.
- Review endpoint evidence for unexpected local access to Telegram Desktop data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2016-10351 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/telegramdesktop/tdesktop/issues/2666CVE reference · x_refsource_MISC
- https://github.com/telegramdesktop/tdesktop/pull/3842/commits/388703b9ca1912a5438e37f9dd54c35805f2c594CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.