New Spectre-v2 Variant Uses JIT Compiler Branch Target Reuse for Cross-Process Data Extraction
Researchers from the Netherlands and Italy have published a scientific paper describing a new attack belonging to the Spectre-v2 class. The original Spectre-v2 technique, demonstrated in 2018, exploits the branch prediction mechanisms in modern CPUs to execute a chosen malicious instruction and then read its results from cache via a side channel.
The new research replaces instruction injection with a method that reuses existing information inside the branch predictor. The required Branch Target Reuse state is created by the operation of a JIT compiler, a scenario previously considered impractical for attacks. The published study demonstrates successful secret extraction when branch prediction features are combined with the cBPF JIT compiler present in the Linux kernel.
The same researchers also examined the SpiderMonkey JIT compiler used in Firefox and the GraalVM engine. The JIT compiler was employed to train the branch predictor, while the actual attack became possible when different code was loaded at the same memory addresses. This created conditions for speculative execution that granted access to secret data.
A practical demonstration targeted the su process on Linux and extracted the hashed root password from CPU cache. The required result was achieved in an average of three to five minutes, which is relatively fast for complex Spectre-class attacks. A full attack was shown using the cBPF compiler. With SpiderMonkey and GraalVM only partial success was recorded: branch predictor training was possible, yet realistic attacks could not be demonstrated.
The researchers confirmed that the attack works on all major modern CPU types, including AMD, Intel, and ARM architectures.
What else happened
Specialists from Kaspersky published an analysis of methods for detecting traces of attacks against 1C servers, extending their earlier research on real incidents. Last week Debian released a record kernel update addressing more than 1,300 vulnerabilities. Dangerous flaws were found in both client and server components of TeamViewer. A zero-day vulnerability in Core Graphics was fixed in iOS and macOS updates. Google closed its bug bounty program for open-source projects it supports due to the large volume of automatically generated reports produced by AI assistants. Critical vulnerabilities were also disclosed in Dell Container Storage Modules, including two issues with a maximum CVSS score of 10 that allow authentication bypass.
Related articles
Researchers Disclose Full Remote Vehicle Takeover Chain in Major Automaker Connected Platform
Security researchers Shubs and Sam Curry discovered a complete attack chain allowing remote control of any connected vehicle from a major undisclosed automaker across Australia and other large markets. The chain began with decompiled Android APK analysis that revealed hardcoded API endpoints under redacted-telematics.com.au and exposed administrative interfaces. Weak access controls in an OpenIDM instance permitted unauthenticated enumeration of user accounts via email, GUID, and phone number lookups. Path traversal bypasses combined with leaked staging credentials granted administrative access to ForgeRock OpenIDM, enabling password resets and full account takeover. Researchers further bypassed MFA using Resource Owner Password Credentials flows and obtained valid mobile application tokens. With these tokens they could issue arbitrary remote commands including unlock, lock, horn activation, and engine start to any vehicle by VIN or license plate.
Nightmare Eclipse Publishes SignDrop Zero-Day in Windows CLFS Driver
Security researcher Abdelhamid Naseri, known as Nightmare Eclipse, has disclosed a new zero-day vulnerability named SignDrop affecting the Common Log File System (CLFS) driver in Windows. The flaw allows attackers to bypass authentication protections introduced by Microsoft in October 2025 and escalate privileges on affected systems. SignDrop exploits the way CLFS handles .cnpf authentication file creation when a new log file is generated, enabling a privileged process to open the file later and create it with SYSTEM rights. The technique can also be abused against any antivirus or EDR engine to disable self-protection mechanisms by making file creation requests appear to originate from the legitimate security process itself. Nightmare Eclipse confirmed the issue works on Windows 11 26H2, Windows 11 26H2 Experimental, and Windows Server 2025 Experimental, impacting an estimated 80 percent of Windows installations. No workaround exists other than waiting for a Microsoft patch, as disabling CLFS protections would reintroduce memory corruption risks. The researcher previously released multiple other zero-days, including BigDiskBuster and RoguePlanet targeting Microsoft Defender.
Telegram Patches RCE Vulnerabilities in HTML Widgets After Researcher Demonstrates Calculator Exploit
Telegram introduced HTML widgets for bots in early November, allowing JavaScript execution inside messages via the QuickJS engine. Security researcher V12 quickly demonstrated remote code execution by launching the system calculator on Android. Pavel Durov responded that no vulnerability existed because the user had to first start the bot, yet server-side fixes were deployed anyway. Multiple use-after-free and use-after-return bugs were identified in QuickJS and QuickJS-ng, some discovered with AI assistance from Claude Fable 5.1 and Mythos 5.2. Telegram isolated the widget engine into a separate process on Android, added syscall filtering, and limited nested graphical effects to prevent crashes. Desktop clients received the fixes across versions 7.4.2 and 7.4.3, while widgets were temporarily restricted server-side. Users are advised to update to Android 13.2.2 or Desktop 7.4.3 and avoid unknown bots.
Telegram Patches Critical QuickJS Sandbox Escape Vulnerability in Android Update 13.2.2
Telegram has released version 13.2.2 for Android to address a high-severity vulnerability in its HTML widgets for bots. The flaw resided in the QuickJS JavaScript engine within Telegram's QuickJS-ng fork and allowed scripts in ordinary messages to break out of the sandbox and execute native code on the device. The root cause was improper handling of the await using construct inside non-async functions, which triggered a use-after-return condition by freeing local variable references while nested functions still accessed the stack. The vulnerable code entered the QuickJS-ng main branch on May 16 as part of explicit resource management support. Security researcher Andreas Rösler discovered the issue during an AI-assisted audit with Anthropic's Claude model that identified 27 findings total. The patch enforces a syntax error on the invalid construct and was merged on November 10, the same day the Android release became available. Although reported against Android 13.2.1, the bug affected every platform using the affected engine fork.