Compromised SIM Cards Exploit Proactive SIM to Steal Files, Execute Code and Force 2G on Smartphones and IoT Devices
Researchers from the University of Birmingham and Fuzzware have shown that a compromised SIM card can take control of certain smartphones and IoT devices by abusing a built-in cellular standard feature. The attack allows file theft, disabling of connectivity, forced downgrade to 2G networks and even arbitrary code execution.
The technique relies on the Proactive SIM capability, which lets the SIM card itself send instructions to the modem. Specifically, the RUN AT command forces the modem to execute AT commands, a control language dating back to the 1980s. This creates a direct, standards-compliant channel from the SIM card to the device hardware.
To validate the findings, the researchers developed the CATana toolkit and evaluated 18 smartphones plus eight cellular-connected devices. The AT command interface was reachable from the SIM on two phones and seven IoT units. In total, four vulnerabilities were discovered and weaponized to achieve code execution, file exfiltration, denial of service and forced 2G downgrade.
On an AUTEL charging station equipped with a Quectel EC25-AFX module, commands from the SIM card resulted in command injection and code execution. The OPPO Reno14 F 5G accepted 198 AT commands and variants, allowing the device to be powered off, the modem stopped or the connection forced to 2G. The downgrade persisted across airplane mode, SIM removal and network setting changes, opening the door to rogue base-station attacks because 2G lacks network authentication.
In the Quectel EG25-G modem, researchers combined SIM-issued commands with a malicious symbolic link to exfiltrate chosen files to an attacker-controlled server. All attacks require prior control of the SIM card, which could be obtained through existing vulnerabilities, physical replacement, remote management infrastructure or supply-chain tampering.
Some manufacturers have already issued patches. GSMA has registered the issue as CVD-2026-0122. The researchers argue that repeatedly patching RUN AT is insufficient and recommend removing the function from device firmware altogether.
Related articles
Enodia: Open-Source Go Tool Automates Service Inventory, EOL Tracking and CVE Correlation
A DevOps engineer has released enodia, a single-binary Go CLI that discovers real versions of services across large heterogeneous environments and correlates them with end-of-life calendars and vulnerability databases. The tool was built after manual Ansible-based inventories and existing solutions such as endoflife.date, nvchecker, Renovate and Uptime Kuma proved insufficient for covering both infrastructure and application services while also providing actionable lifecycle, patch and branch status. Enodia uses product-specific probes for 123 technologies including PostgreSQL, MySQL, MariaDB, Jira, Confluence, Bitbucket, VMware vCenter, ESXi, pfSense and multiple Linux distributions, falling back to a generic URL-plus-regex probe when needed. Data collection is deliberately separated from evaluation so that inventory.jsonl files can be generated inside air-gapped networks and later analysed where CVE feeds are available. The project also contributed dozens of missing products and corrected EOL dates to the endoflife.date project and integrates both NVD and Russia’s FSTEC BDU vulnerability databases. Special handling was added for MySQL/MariaDB connection-error counters, version-string masquerading, and vendor-specific update nomenclature to avoid false reports.
Telegram Voice Call Flaw Allows Remote Code Execution on Android Devices
Security researchers disclosed a vulnerability in Telegram for Android that enables remote code execution on a victim's device simply by answering a voice call. The attacker requires only a standard account, and the flaw was present in versions 8.6.2 through 12.10.3 released between March 2022 and September 2026. Telegram addressed the issue in version 12.10.4, released at the end of September 2026. The root cause lies in improper handling of the MediaState message exchanged during calls, specifically when processing rotation values and missing video state fields, leading to out-of-bounds memory reads. The same underlying fix was deployed earlier to shared call libraries, iOS, and desktop clients, but reached Android later. Researchers confirmed the impact only on private calls running on ARM64 Android devices, with no evidence of exploitation in the wild or public CVE assignment as of October 29, 2026.
360 Security Cloud Opens PHP2Shell Vulnerability Self-Check Platform to Government and Enterprise Users
360 Security Cloud has launched a dedicated self-assessment platform that allows organizations to scan their PHP-based websites and systems for the PHP2Shell vulnerability. The service is now available to government agencies, large enterprises, and small-to-medium businesses. Users can apply by scanning a provided QR code to determine how many of their assets run PHP, identify affected versions, and check whether any systems have already been compromised. The platform addresses key questions about exposure: the number of PHP-powered sites and systems, the presence of vulnerable versions, and signs of prior intrusion. The announcement emphasizes that the tool helps organizations proactively assess risk without requiring external assistance. The original Chinese report was published on October 30, 2026, and the service is positioned as a practical response to ongoing PHP-related security concerns.
Liferay Community Edition Misconfiguration Exposes Plaintext Passwords in Government Systems via CWE-319
A detailed analysis reveals how the use of Liferay Community Edition in a closed government information system led to the transmission of user passwords in plaintext through transactional emails. The issue stemmed from default notification templates that included the [$PASSWORD$] macro, combined with unadjusted system variables pointing to localhost instead of the production domain. Despite proper OAuth 2.0 delegation and CSRF protections, the misconfigured password change workflow sent permanent credentials in clear text to user inboxes. The root cause was traced to custom portlets that incorrectly reused the New Password Notification trigger intended only for administrator-initiated resets. Remediation involves removing the password macro from email templates and updating portal-ext.properties to enforce production host settings. The case highlights how open-source enterprise platforms require thorough hardening beyond initial code audits when deployed in high-security environments.