<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor-Patch on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vendor-patch/</link><description>Recent content in Vendor-Patch on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 29 Sep 2026 16:53:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vendor-patch/index.xml" rel="self" type="application/rss+xml"/><item><title>Kiteworks Patches Critical Flaw Found During Emergency Shutdown</title><link>https://curasec.metacog.co.kr/insights/2026-09-29-kiteworks-fixes-critical-flaw-found-during-nine-hour-precaut/</link><pubDate>Tue, 29 Sep 2026 16:53:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-29-kiteworks-fixes-critical-flaw-found-during-nine-hour-precaut/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If Kiteworks is in your stack, verify whether the affected capability (enabled for &amp;lt;1% of customers) is active in your deployment and apply the available patch this sprint; no exploitation signals yet but federal involvement warrants prompt action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If Kiteworks is in your vendor portfolio, contact them to confirm whether your tenant used the affected capability and request written attestation that the fix has been applied to your environment.&lt;/li>
&lt;/ul></description></item></channel></rss>