<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit-Chain on CuraSec</title><link>https://curasec.metacog.co.kr/tags/exploit-chain/</link><description>Recent content in Exploit-Chain on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 16:03:46 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/exploit-chain/index.xml" rel="self" type="application/rss+xml"/><item><title>Ivanti Connect Secure: Three Flaws Chained for Unauthenticated Root Access</title><link>https://curasec.metacog.co.kr/insights/2026-10-31-attackers-chain-three-ivanti-connect-secure-flaws-to-gain-un/</link><pubDate>Sat, 31 Oct 2026 16:03:46 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-31-attackers-chain-three-ivanti-connect-secure-flaws-to-gain-un/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Ivanti Connect Secure is a common enterprise VPN appliance; CISA KEV listing plus active exploitation plus a public GitHub PoC makes this urgent — patch ICS immediately and audit appliance logs and filesystem integrity for signs of pre-patch compromise.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active exploitation of an edge VPN device means assume-breach posture is warranted — hunt for anomalous outbound connections and lateral movement from ICS appliance IPs since the KEV listing date, and check for Ivanti-specific persistence IOCs from prior campaigns (SPAWN/BUSHWALK malware families).&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Ivanti Connect Secure has systemic enterprise reach; confirm with your network/infra team whether ICS is in use, obtain a patch-status attestation this week, and brief leadership — this class of Ivanti exploitation has previously generated board-level headlines.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-111357 — CISA KEV: listed, EPSS 0.01, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>