Dell Patches Six Critical Flaws in Container Storage Modules for Kubernetes
Dell has addressed six vulnerabilities in its Container Storage Modules (CSM), the software suite that connects Dell storage arrays to Kubernetes clusters. Two of the flaws received the highest possible CVSS score of 10.0, enabling remote attackers to gain administrative control without any authentication.
The first critical issue, CVE-2026-63688, stems from missing authentication on the gRPC server within the storage authorization component. An unauthenticated remote attacker can retrieve administrator credentials for every registered storage backend array.
The second 10.0-rated vulnerability, CVE-2026-63692, involves the absence of authentication in both the authorization proxy and the tenant service. Successful exploitation grants complete administrative control over the very service responsible for managing access controls.
A third high-severity flaw, CVE-2026-67269 (CVSS 9.9), results from improper privilege management in the custom resource reconciler. A low-privileged attacker can submit a single malicious resource definition and escalate privileges to root on all nodes, reaching every device in the cluster.
Two additional issues rated 9.8 originate from embedded secrets in the code. CVE-2026-54472 contains hardcoded credentials inside the authorization module, while CVE-2026-61421 exposes the private key used to sign JWT tokens, allowing attackers to forge valid authentication credentials.
The final vulnerability, CVE-2026-67273 (CVSS 9.6), resides in the template engine and permits reading Kubernetes secrets across the entire cluster as well as creating cluster-scoped permissions.
All versions prior to 1.17.0 are affected. The fixes are included in version 1.18.0. No alternative mitigations are available. Dell strongly advises rotating all JWT signing keys after the update, as the previous keys should be treated as publicly known.
Related articles
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.
Node.js Patches 16 Vulnerabilities Exposing TLS Private Keys and Cross-Connection Data
The Node.js project has released fixes addressing 16 vulnerabilities, seven of which are rated high severity. The most critical issue, CVE-2026-123864, allows an unauthenticated client to read memory from other HTTPS connections, potentially exposing TLS private keys and requests belonging to other users. Three supported release lines were affected, and exploitation requires a specific application code pattern involving res.flushHeaders() and res.end() calls before the request body is fully received. Additional high-severity flaws include CVE-2026-123863, which crashes HTTP/2 servers, CVE-2026-123866 that leaks server memory chunks to clients, and CVE-2026-123865 that causes permanent memory and file descriptor leaks in HTTP/2 servers. Several other CVEs affect TLS renegotiation, SNI callbacks, and file streaming functions. The project states that end-of-life branches including 20.x and 25.x remain vulnerable with no patches available.