Telegram Desktop Bug Deletes 800 GB of User Data Due to Spelling Checker Path Error
A Windows user reported losing nearly 800 GB of data after updating Telegram Desktop. Files began disappearing from the custom directory C:\custom immediately after launching the messenger, while folders themselves remained intact.
Tracing the culprit
By monitoring application launches, the user isolated the issue to Telegram Desktop. Reinstalling the application to a separate location and creating test files confirmed that Telegram continued to target the original folder. Testing across versions showed the problem appeared after updating from 6.9.4 to 7.1.1.
Process Monitor investigation
Running Process Monitor revealed that Telegram.exe opened C:\custom, enumerated its contents, requested delete permissions, and attempted recursive removal. Stack traces pointed directly inside the Telegram binary, ruling out malware.
Root cause in spell checking
The deletion originated from the lib_spellcheck library. Telegram stores user-added words in a file named custom. In version 7.1.0, changes to support Windows native spell checking introduced a logic error: the path to the internal dictionary was set after an early return when the system spell checker was active.
With an empty working directory path, the code constructed the string /custom. Qt resolved this to C:\custom on the root of the current drive. The subsequent check if (QFileInfo(path).isDir()) { QDir(path).removeRecursively(); } then deleted the entire folder instead of a small internal dictionary directory.
Fix and impact
Developers corrected the issue in commit 9c316281 by setting the path before the return and added an empty-path guard in lib_spellcheck. The faulty versions remained available for roughly 66 hours. The bug was confirmed only on Windows with native spell checking enabled.
The case demonstrates how individually reasonable decisions—storing custom words, cleaning damaged directories, and using recursive deletion—combined into severe data loss when path validation was absent.
Related articles
Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison
An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.
VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server
Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.
September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication
The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.
API Token Lifecycle: From Issuance to Revocation and Secure Management
The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.