Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: proof-of-concept (2 articles)Clear

LibreOffice and OpenOffice flaws let malicious spreadsheets run code without macro warnings

Researchers disclosed CVE-2026-63277 in LibreOffice and CVE-2026-59265 in Apache OpenOffice, flaws that let a malicious spreadsheet run code without triggering macro warnings. The attack chains legitimate features: a spreadsheet defines a database range that downloads an ODB database file from a web address, and that file references a JDBC driver, causing automatic download and execution of attacker-controlled Java code. LibreOffice fixed the issue in versions 26.2.5 and 26.8.0 on October 5, while Apache OpenOffice remains affected through 4.1.16 with 4.1.17 still in testing. The technique exists only as a proof of concept, credited to researchers at V12 and Codean Labs.

Check
Upgrade LibreOffice to 26.2.5 or 26.8.0, and for Apache OpenOffice avoid opening untrusted spreadsheets until 4.1.17 ships, disabling automatic database and JDBC features.
Affected
Vulnerable LibreOffice and OpenOffice versions let a crafted spreadsheet download a database file and JDBC driver that runs attacker Java code without any macro warning.
Fix
Apply the LibreOffice fixes, restrict or disable JDBC and external database connections, and treat spreadsheets from untrusted sources as potentially executable content.

GhostLock proof-of-concept abuses Windows file-sharing API to disrupt file access without encryption

A researcher at Israel Aerospace Industries published a proof-of-concept tool called GhostLock that uses a legitimate Windows API call to make files unreadable without encrypting anything. The technique abuses the dwShareMode parameter of CreateFileW - setting it to 0 grants the calling process exclusive access, so every other user or app trying to open the file gets a sharing violation. GhostLock automates this recursively across SMB shares from a standard domain user account, no elevation required. Researcher Kim Dvash frames it as a disruption attack, not destructive - data is not lost, but operational downtime can mirror a ransomware incident.

Check
Review your EDR and SIEM detection rules for behavior-based ransomware indicators. Verify they cover sharing-violation spikes and ShareAccess=0 file-open counts, not just mass file write or encryption activity.
Affected
Windows file servers and SMB shares in environments where any standard domain user account can authenticate. No CVE has been assigned - GhostLock abuses intended Windows file-sharing behavior, not a flaw. Behavioral detection systems focused on mass writes or encryption operations will not flag this attack pattern; the attack also requires no elevation.
Fix
Implement detection at the file server layer: monitor per-session open-file counts with ShareAccess=0 - the reliable signal Dvash identifies, which lives in storage platform management interfaces, not Windows event logs or EDR telemetry. Pull the SIEM queries and NDR rule from the GhostLock whitepaper as a detection template. Limit which domain user accounts have read or write access to critical shares.