<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🟡 Medium: PEERSTITCH Malware Deployed via FortiOS Flaw Bypasses Checks on Tagged VPN Sessions]]></title><description><![CDATA[<p dir="auto">A suspected advanced threat actor is exploiting a security flaw in <strong>Fortinet FortiOS</strong> to deliver a previously unreported memory-resident <strong>ARM64</strong> malware tracked as <strong>PEERSTITCH</strong>.</p>
<p dir="auto">The vulnerability in question is <strong><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-61624" target="_blank" rel="noopener noreferrer nofollow ugc">CVE-2025-61624</a></strong>, a path traversal flaw in the command line interpreter affecting <strong>FortiOS</strong>, <strong>FortiPAM</strong>, <strong>FortiProxy</strong>, and <strong>FortiSwitchManager</strong>. It carries a <strong>CVSS score of 5.4</strong>. According to the reporting, successful exploitation could allow an attacker to bypass checks on tagged VPN sessions.</p>
<p dir="auto">Key points from the research so far:</p>
<ul>
<li>The malware, <strong>PEERSTITCH</strong>, is described as memory-resident and compiled for <strong>ARM64</strong> architectures, and had not been publicly documented before this campaign.</li>
<li>The flaw is a path traversal issue in the CLI interpreter shared across multiple Fortinet products, not just FortiOS.</li>
<li>The actor behind the activity is described as suspected advanced, though attribution has not been confirmed.</li>
</ul>
<p dir="auto">Defenders running any of the affected Fortinet products should treat this as a priority: review exposure of management interfaces, monitor for unusual CLI activity, and watch for suspicious processes or artifacts consistent with in-memory ARM64 payloads. Because the malware resides in memory, traditional file-based scanning may miss it entirely, so behavioral detection and logging of tagged VPN session activity are worth prioritizing.</p>
<p dir="auto">Source: <a href="https://thehackernews.com/2026/10/attackers-exploit-fortios-flaw-to.html" target="_blank" rel="noopener noreferrer nofollow ugc">The Hacker News</a></p>
<p dir="auto">Has anyone in the community observed unusual CLI or VPN session behavior on their Fortinet appliances, and how are you approaching detection for memory-only payloads like this?</p>
]]></description><link>https://xploitlk.com/topic/714/medium-peerstitch-malware-deployed-via-fortios-flaw-bypasses-checks-on-tagged-vpn-sessions</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:18:01 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/714.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 17 Oct 2026 02:30:20 GMT</pubDate><ttl>60</ttl></channel></rss>