Loading vulnerability…
In Telegram app version 5.10 for Android and iOS, the 'Privacy > Phone Number' feature incorrectly indicates that a user's phone number is hidden from everyone ('Nobody'), but attackers can still enumerate and discover users' phone numbers via the Group Info feature. By systematically adding a large set of phone numbers (e.g., all numbers in a region) to a group, an attacker can determine which numbers are associated with Telegram accounts, thus bypassing the intended privacy control.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2019-15514, an information disclosure vulnerability affecting all versions of Telegram Messenger. The exploit allows an attacker to discover the phone number associated with a specific Telegram user ID or username by brute-forcing possible phone numbers and checking which one is linked to the target. The repository consists of two main Python scripts: 1. num_gen.py: Generates a wordlist of possible phone numbers based on a given prefix, suffix, and number of unknown digits. The output is a text file containing all possible combinations. 2. brute.py: Uses the Telethon library to connect to the Telegram API (optionally via a proxy), imports batches of phone numbers as contacts, and checks if any of the imported contacts match the target user ID or username. If a match is found, the script outputs the discovered phone number. The exploit is multi-threaded, supports resume capability, and can use proxies to bypass regional blocks. It requires the attacker to have a valid Telegram account and API credentials. The README provides detailed instructions for configuring and running the scripts. Several endpoints are referenced, including Telegram API documentation, proxy sources, and related tools. The exploit is a working proof-of-concept and demonstrates a real privacy issue in Telegram's contact import mechanism.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.