Telegram widget flaw may have been used to push WebRAT malware
Telegram says the Android problem is fixed, but Kaspersky advises against launching widgets until a full fix ships.
A flaw that lets an attacker run their own code on someone else's machine over a network, without physical access.
It is among the most serious kinds of vulnerability, because it can hand over control of the whole system.
Telegram says the Android problem is fixed, but Kaspersky advises against launching widgets until a full fix ships.
Servers running Apache 2.4.55 to 2.4.70 with HTTP/2 enabled should upgrade to 2.4.71, and the archived mod_h2 project has no fixed release.
The intrusion reached data from about 100 Private Chat accounts and 18 agents, and shows that a confidential-computing enclave does not shield bugs in the software inside it.
Customers on both hosted and on-premises N-central must stay offline until a hotfix is confirmed, which N-able expects around midday on November 10.
Administrators must check each user's copy and any provisioned copy, because Windows Update will not deliver the fix.
Two GMS vulnerabilities will stay open on an end-of-life platform, while Dimension users wait for a fix to a critical Linux kernel bug.
Operators running end-of-life PHP versions now have patches reaching back to 7.4, and most installations online are on unsupported releases.
Phones on Android 14 through 17 need the security patch dated 2026-11-01 or later, and the second tranche must follow for kernel and chipset fixes.
The top-tier reward targets attacks needing no prior access, stolen credentials or user action, a bar that raises the stakes for cloud security research.
Operators still on unpatched GitLab releases remain exposed, with more than 1,000 internet-facing servers yet to be fixed.
Organisations running internet-exposed Oracle EBS instances face a remotely exploitable critical flaw that is now being probed, so the October patch matters now.
Federal agencies have until October 29, 2026 to patch, and tens of millions of PHP services still run a vulnerable version.
Many sites were running end-of-life PHP versions, so the one-point-release fix could not be applied quickly everywhere.
Operators running industrial control systems now have to check which vendor products carry the PHP engine flaws, several of which still lack full patches.
Operators running unpatched PHP are exposed, and a further flaw has no patch yet, only a configuration workaround.
Organisations running unpatched PHP servers face active exploitation, and defenders are being told to watch for a specific pattern of errors in their logs.
Operators running any unpatched PHP since version 5.4 are exposed, and the advisories say updating and restarting every worker is the only safe fix.
Server operators running affected configurations must disable one setting now, while attackers have so far mostly probed the PHP2Shell flaws without confirmed compromises.
Defenders should not treat the public disclosure date as the earliest point at which the flaws were exploited.
Self-managed administrators on the affected releases need to upgrade, since over 2,700 Community Edition instances are publicly visible.