安全客•August 13, 2026•🇨🇳Translated from Chinese

Malicious SIM Card Commands Hijack EV Chargers and IoT Modules via Legacy AT Interface

University of Birmingham researchers, working with Fuzzware, have shown that a malicious SIM card can take full control of EV charging stations, industrial routers and vehicle telematics units by exploiting a 1981-era AT command interface still present in modern cellular modules.

26 devices tested, nine compromised

The team inserted modified SIM cards into 26 devices comprising 18 smartphones and eight cellular modules. Nine devices accepted and executed commands sent from the SIM. Six of the eight modules were vulnerable, five of them Quectel units taken from commercial EV chargers, industrial routers and automotive T-Box systems. Only three phones were affected: OPPO Find X5, OPPO Reno 14 F 5G and Asus Zenfone 9. iPhone and Pixel devices proved immune. All nine vulnerable devices used Qualcomm modems, yet five other Qualcomm phones resisted the commands, indicating the issue stems from vendor-specific configuration rather than the chipset itself.

RUN AT: a standards-compliant backdoor

AT commands, first defined by Hayes in 1981, remain the native control language for every cellular module. The RUN AT proactive command, explicitly allowed by 3GPP specifications, lets the SIM instruct the modem to run any AT string. When the baseband cannot process a command it is forwarded to the application processor, typically an ARM Cortex-A7 running a full Linux environment. This architecture turns the tiny SIM into a privileged console with direct access to the host operating system.

Three working attack chains

On an Autel MAXI US AC W12-L-4G charger the atfwd_daemon on the Quectel EC25 module contained an unsafe format string that allowed shell escape via a newline character, granting code execution driven entirely by SIM-originated commands. On the OPPO Reno 14 F 5G an AT+COPS command permanently locked the device to 2G networks, defeating airplane mode, manual network selection and SIM disablement, thereby enabling subsequent rogue-base-station attacks. On the Quectel EG25-G a root TFTP daemon combined with the built-in AT+QSMTP command permitted arbitrary file read and email exfiltration once a malicious symlink was present in the filesystem.

Disclosure timeline and vendor response

Vendors were notified in March 2026 and GSMA was informed in May. The flaws are tracked as CVE-2026-57550 (Qualcomm channel) and CVD-2026-0122 (GSMA). As of 10 August no public advisories have been published. Google and OPPO classified the reports as informational; Semtech confirmed the issue will be addressed with Qualcomm patches; Quectel acknowledged the problem but restricts its security portal to logged-in users. High has introduced a default-disabled configuration for future modules, yet existing stock remains exposed.

Recommended actions for asset owners

  • Inventory every cellular-equipped device, recording module model, firmware version and physical accessibility of the SIM slot.
  • Contact module suppliers to determine whether RUN AT is enabled in shipped firmware and request a timeline for patches.
  • Apply physical tamper protection such as epoxy or locks on unattended equipment and establish reliable over-the-air update channels.

Related articles

Habr•Vulnerabilities & Exploits

Chrome Researcher Edits Own VRP Reward to $1.3M in Bug Tracker Prank, Triggering AI Misinformation Spread

Security researcher Lyra Rebane, who has disclosed 14 CVEs in Chrome, reported a logical flaw in the Background Fetch API in 2022 that could enable browser-based botnets. Google awarded $1,000 after the issue was fixed in February 2026, but the researcher later received verifier rights in the Buganizer tracker. She jokingly set the vrp-reward field to $1,333,337, the largest amount in Google VRP history. The tweet about the edit went viral and was picked up by AI news generators and Google search, which began listing her as a millionaire. Community Notes initially flagged the post before an experimental AI note incorrectly claimed the screenshot was edited. The incident highlights how social media amplification and AI systems can turn a harmless joke into persistent misinformation across search engines including Kagi, DuckDuckGo, and Bing.

Securitylab•Vulnerabilities & Exploits

Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK

Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.

Habr•Vulnerabilities & Exploits

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.

Securitylab•Vulnerabilities & Exploits

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.