Telegram Desktop Bug Deletes Up to 800 GB of User Data on Windows Due to Spellcheck Library Error
A dangerous configuration error in Telegram Desktop for Windows led to the recursive deletion of nearly 800 GB of user data stored in the C:\custom directory. Home users reported that executable files began disappearing while folder structures remained, gradually emptying entire project and application directories.
The root cause was traced to the lib_spellcheck library responsible for handling user-added dictionary words in a file named custom. Following changes in version 7.1.0, the Windows code passed an empty path string to the spellchecker; Qt then appended /custom, resolving it to the absolute path C:\custom. When the library encountered a directory instead of the expected dictionary file, it executed removeRecursively(), systematically deleting all accessible contents.
Analysis with Process Monitor confirmed that Telegram Desktop was opening the path, traversing subdirectories, and requesting deletion rights without any malicious intent or updater malfunction. The flaw was limited to Windows builds containing the integrated spellchecker and existed in versions 7.1.0 and 7.1.1 for approximately 66 hours.
The researcher virtual-anvil submitted detailed logs and opened ticket #31170. Developers acknowledged the issue, implemented fixes that ensure the path is validated before the function is called and that the library is blocked from operating on an empty address, and released the corrected build in Telegram Desktop 7.1.2. Affected Windows users are strongly recommended to update without delay.
Related articles
Unemployed AppSec Engineer Releases fe-zk Library to Catch Soundness Bugs in Zero-Knowledge Verifiers
A Russian developer identifying as 0xItsss, currently unemployed after months of rejections for AppSec, Rust, and backend roles, has published fe-zk, a verifier library and generator for the Fe smart-contract language. The project implements Groth16, PLONK, halo2-KZG, KZG openings, and FRI/STARK verifiers for Plonky3, all generated from existing verifying keys with built-in tests. The author highlights systemic soundness failures in on-chain verifiers, including missing public-input range checks, curve subgroup validation, Fiat-Shamir transcript coverage, and precompile return-length checks, citing the Frozen Heart class of transcript attacks. By leveraging Fe’s traits, const generics, static_assert, and private fields, fe-zk turns many of these rules into compile-time errors rather than auditor findings. The library ships with verified integrations for Semaphore v4, Tornado Cash mainnet proofs, and a zk Game of Life demo, plus BLS12-381 precompile wrappers from EIP-2537.
Chrome Researcher Edits Own VRP Reward to $1.3M in Bug Tracker Prank, Triggering AI Misinformation Spread
Security researcher Lyra Rebane, who has disclosed 14 CVEs in Chrome, reported a logical flaw in the Background Fetch API in 2022 that could enable browser-based botnets. Google awarded $1,000 after the issue was fixed in February 2026, but the researcher later received verifier rights in the Buganizer tracker. She jokingly set the vrp-reward field to $1,333,337, the largest amount in Google VRP history. The tweet about the edit went viral and was picked up by AI news generators and Google search, which began listing her as a millionaire. Community Notes initially flagged the post before an experimental AI note incorrectly claimed the screenshot was edited. The incident highlights how social media amplification and AI systems can turn a harmless joke into persistent misinformation across search engines including Kagi, DuckDuckGo, and Bing.
Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK
Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.
F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway
Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.