Telegram Bug Floods iPhones with Fake Notifications, Causing Severe Overheating and Battery Drain
A persistent bug in the Telegram messaging app has been causing iOS devices to overheat dramatically and rapidly drain their batteries by spamming hundreds of false push notifications in the background.
The issue triggers constant English-language alerts reading "You have a new message" even when users have Russian language settings enabled and message previews turned off, rendering the notifications useless and filling the notification shade with chaos.
Reports of the problem first emerged in May but intensified after the release of Telegram version 12.9, which appears to create an infinite loop in background processes that overworks the CPU.
Affected users report battery losses of up to 11 percent within 30 minutes of idle time, with some devices becoming hot enough that Apple automatically pauses charging until temperatures drop.
One journalist even resorted to using a gaming controller with a built-in fan to keep an iPhone cool enough to charge during the ordeal.
Temporary Workaround
The only temporary workaround involves the following steps:
- Go to Telegram Settings → Data and Storage → Storage Usage and clear the cache.
- Ensure you have access to your password or recovery codes via email or other linked devices.
- Delete the Telegram app from the device.
- Reinstall it from the App Store and log back in.
While this approach helps many users, the bug has been known to return after one or two weeks for some, leaving the community waiting for a proper fix from the Telegram development team.
Related articles
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.
NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2
On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.
Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4
China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.
Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors
The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.