<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Libreoffice on CuraSec</title><link>https://curasec.metacog.co.kr/tags/libreoffice/</link><description>Recent content in Libreoffice on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 17:10:43 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/libreoffice/index.xml" rel="self" type="application/rss+xml"/><item><title>LibreOffice/OpenOffice PoC: Spreadsheets Execute Code, No Macro Warning</title><link>https://curasec.metacog.co.kr/insights/2026-10-06-libreoffice-and-openoffice-flaws-let-malicious-spreadsheets/</link><pubDate>Tue, 06 Oct 2026 17:10:43 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-06-libreoffice-and-openoffice-flaws-let-malicious-spreadsheets/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your environment runs LibreOffice or OpenOffice with Java support enabled, audit those deployments and disable Java as a mitigation now; monitor for a vendor patch and apply it promptly when released. No active exploitation yet, but the attack surface (malicious file opened by a user) is realistic.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or published IOCs yet, so there is nothing actionable to hunt; worth tracking in case threat actors weaponize this for phishing lure campaigns delivering malicious spreadsheets.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>