Telegram Voice Call Flaw Allows Remote Code Execution on Android Devices
Security researchers disclosed a vulnerability in Telegram for Android that allows remote code execution on a victim's device after the user answers a voice call. The attacker needs only a regular account, with no special privileges required.
The flaw was present across versions 8.6.2 to 12.10.3, spanning releases from March 2022 through September 2026. Telegram issued the fix in version 12.10.4 at the end of September 2026. As of the disclosure on 29 October 2026, no CVE identifier had been assigned and no confirmed real-world attacks had been observed.
The root cause resides in the code that parses short messages exchanged between clients during a call. One such message, MediaState, reports microphone mute status, camera activation, and video rotation. The vulnerable implementation mishandled absent fields and read memory it should not have accessed.
According to The Hacker News, the defect is visible in the published source of version 12.10.3: when a rotation value is present, the code checks it and then reads the video state field even if that field is missing. Version 12.10.4 reads the rotation value from the correct field instead.
The underlying library fix was merged on 21 April 2026. It reached iOS in version 12.7 in May, the desktop application in 7.0.1 in July, and Android only in September. Researchers verified the issue solely on private calls running on ARM64 Android devices and found no indication that iOS, desktop, or group calls are affected.
No technical exploit analysis has been published, and the video demonstration does not disclose the exact versions used, so the link between the memory error and code execution rests on the researchers' report. Users should check the version number at the bottom of the Settings screen and update to 12.10.4 or later. Organizations managing corporate devices should inventory their fleet, as the affected range covers four and a half years of releases and devices without automatic updates remain exposed.
This issue is distinct from CVE-2026-111105, a separate 7.0-severity flaw in Telegram's animation library disclosed by the Zero Day Initiative.
Related articles
WordPress Patches Race Condition in Core Update Process Enabling Unauthenticated Remote Code Execution
WordPress addressed a critical race condition vulnerability in its core update mechanism on October 28, 2026, that could allow remote code execution without authentication. The flaw affects the automatic update process used by the majority of installations, exposing a temporary installer during file extraction to a predictable folder. Wordfence recorded 60,471 exploitation attempts within the first 24 hours after disclosure. The issue was discovered by researcher Umut Bayram and fixed across multiple branches including version 7.1.4, which bundles 22 security patches. Mitigations include immediate updates, restricting public access to the wp-content update directory, and ensuring application firewall coverage. Versions 4.6 and earlier receive no further security updates.
Google Releases November Android Security Patch Fixing 216 Vulnerabilities Including Critical Zero-Click Flaws
Google has issued its November security update for Android, addressing a total of 216 vulnerabilities with 23 classified as critical. The patch resolves multiple remote code execution flaws that require no additional privileges or user interaction, qualifying as zero-click attacks. Specific fixes include CVE-2026-58868 in the Framework component and CVE-2026-58876 along with CVE-2026-58936 in the System component, all impacting Android versions 14 through 17. Additional patches cover privilege escalation, information disclosure, and denial-of-service issues across the kernel, Bluetooth, virtualization layers, and chipsets from MediaTek and Qualcomm. No evidence of in-the-wild exploitation has been noted in the bulletin, yet the critical nature of the remote code execution bugs warrants immediate attention. Users must verify the 2026-11-05 patch level or newer in device settings, as simply running the latest Android version does not guarantee all fixes are installed. Some updates arrive via Google Play system updates while others depend on device manufacturers.
Backdoor with Password 123456 and Hardcoded Keys: How AI Cracked 'Encrypted' USB Drives
An AI agent rapidly discovered critical cryptographic weaknesses in multiple USB encryption and copy-protection products, including hardcoded backdoor accounts and keys that bypassed user passwords entirely. In the SecZure YutianDun drive, two hidden accounts with passwords 123456 and SECZURE.COM allowed full decryption of files without the administrator password. NetacFileLock used a fixed AES-256 key embedded in the binary, ignoring the user password completely while also logging passwords in plaintext and employing ECB mode. KakaSoft USB Copy Protection relied on a modified MD5 implementation with altered shift constants and a hardcoded internal password derived from an embedded seed, enabling full Blowfish decryption without any user input. Nexcopy stored its Triple DES content key and IV in an encrypted configuration file protected only by a fixed 32-byte certificate inside the viewer application. The AI completed analyses in minutes that previously required hours of manual time-travel debugging and reverse engineering.
CVE-2026-98432: Temporary nftables Filter with Auto-Rollback for Ubuntu Servers
Administrators are deploying a temporary nftables-based mitigation for CVE-2026-98432 on Linux systems while awaiting official kernel patches. The filter drops IPv4 TCP packets with IP header length exceeding five, reducing exposure to the vulnerability. The procedure includes verifying kernel status via Canonical, preparing rollback commands, and using systemd timers to automatically remove the table after five minutes if connectivity is lost. Steps cover syntax validation with nft --check, integration with existing firewall configurations, and post-reboot verification to ensure the temporary table persists without interfering with ufw or Docker rules. Red Hat guidance on discarding packets containing IP options is referenced as a complementary measure. The process is designed for single-server testing before scaling to production fleets, with explicit instructions to avoid flush ruleset operations that could disrupt other tables.