<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exchange-Server on CuraSec</title><link>https://curasec.metacog.co.kr/tags/exchange-server/</link><description>Recent content in Exchange-Server on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 01 Sep 2026 15:28:52 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/exchange-server/index.xml" rel="self" type="application/rss+xml"/><item><title>22,000 Microsoft Exchange Servers Exposed to Auth Bypass Hijack</title><link>https://curasec.metacog.co.kr/insights/2026-09-01-nearly-22-000-microsoft-exchange-servers-vulnerable-to-hijac/</link><pubDate>Tue, 01 Sep 2026 15:28:52 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-01-nearly-22-000-microsoft-exchange-servers-vulnerable-to-hijac/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If you run on-premises Exchange, audit internet-facing instances and apply the patch for this authentication bypass before exposure becomes exploitation; the scale of 22,000 unpatched servers makes this an attractive target even without current KEV or PoC signals.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs or confirmed active exploitation are cited, so there is no hunt to run today; file the attack surface (full mailbox hijack via auth bypass) to inform detection design if exploitation activity emerges.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Confirm this quarter whether your organization runs on-premises Exchange and whether it is patched; the breadth of exposed servers (22,000 globally) makes this a likely board or customer question if exploitation picks up.&lt;/li>
&lt;/ul></description></item></channel></rss>