<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patch on CuraSec</title><link>https://curasec.metacog.co.kr/tags/patch/</link><description>Recent content in Patch on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 09:49:54 -0500</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/patch/index.xml" rel="self" type="application/rss+xml"/><item><title>Zimbra Classic Web Client critical XSS flaw requires patching</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-zimbra-urges-customers-to-patch-critical-web-client-xss-flaw/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-zimbra-urges-customers-to-patch-critical-web-client-xss-flaw/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Critical XSS in Zimbra Classic Web Client affects organizations running on-prem Zimbra Collaboration; no KEV listing or public PoC in enrichment signals, so patch on your normal critical cycle — apply the vendor-supplied update to your Zimbra instance this sprint.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>