LibreOffice and Apache OpenOffice Flaws Enable Remote Code Execution via Malicious Spreadsheets Without Macro Warnings
Two vulnerabilities allow attackers to execute arbitrary code simply by opening manipulated office documents, bypassing the usual macro security warnings. The flaws affect LibreOffice Calc and Apache OpenOffice through their integration with Java and the way these applications resolve certain components when loading untrusted files.
CVE-2026-63277 impacts LibreOffice and permits a crafted spreadsheet to trigger loading of a Java database driver from a remote location. The root cause lies in class path handling: an attacker-controlled entry can point outside the local system, causing the application to fetch and execute classes from an external source. The fix enforces that every class path entry must be a file-type URL, effectively blocking remote class loading.
Users should update LibreOffice to version 26.2.5 or 26.8.0 or later. These releases also harden handling of external data links and JDBC connectors in Calc, reducing exposure in environments that regularly exchange spreadsheets containing database connections.
CVE-2026-59265 affects Apache OpenOffice 4.1.16 and earlier, enabling local or remote code execution when a malicious document abuses the Java integration. A stable patch is planned for 4.1.17, currently available only as a release candidate. Until then, administrators should disable Java support in OpenOffice wherever it is not strictly required.
Additional defensive steps include limiting Java usage across office suites on endpoints that frequently open attachments, enforcing strict policies against opening files from untrusted origins, and applying application isolation where feasible. Running office applications with the lowest possible privileges further contains any successful exploitation to the user’s permission boundary.
Related articles
Four Characters Bypass SSRF Filter: IPv6 Zone and netip.Prefix.Contains in Go
A vulnerability tracked as CVE-2026-126799 affects Gotenberg versions 8.31.0 through 8.37.0 and allows attackers to bypass SSRF protections by appending an IPv6 zone identifier to addresses such as [::%251]. The flaw stems from how Go's net/netip package handles zone information in methods like Prefix.Contains and IsUnspecified, which ignore or mishandle the zone component. Researchers reproduced the issue on Go 1.26.11 and 1.27.4, showing that addresses with zones like ::%1 or fec0:1234::3%eth0 evade common allow-list checks used in webhooks, link previews, and URL proxies. The root cause lies in documented behavior where netip.Prefix.Contains returns false for any address carrying a zone, while some methods like IsLoopback remain zone-agnostic. Fixes include stripping the zone with WithZone before classification, rejecting zones in URLs outright, and adding a second check inside net.Dialer.Control. The same pattern appears in many Go projects, making the issue broader than a single Gotenberg bug.
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.