<?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[FBI: Ongoing FortiBleed attacks lock out FortiGate VPN admins]]></title><description><![CDATA[<p dir="auto">The <strong>FBI</strong> has issued a new warning that <strong>FortiBleed</strong> attacks remain active, targeting internet-exposed <strong>Fortinet FortiGate</strong> firewalls and SSL VPN gateways. The campaign focuses on devices that are reachable from the public internet, with attackers moving to lock legitimate administrators out of the very appliances they are supposed to manage.</p>
<p dir="auto">According to the advisory, the activity is ongoing rather than historical, meaning organizations running affected <strong>FortiGate</strong> systems should treat this as an active threat. The core impact described is administrative lockout: once intruders gain a foothold, they can modify credentials and access controls so that real admins are shut out, complicating both detection and recovery.</p>
<p dir="auto">Because the source material does not provide specific CVE identifiers or affected version numbers for this campaign, administrators should rely on Fortinet's own guidance and the FBI's bulletin for authoritative technical details rather than any third-party list of identifiers.</p>
<p dir="auto">Recommended steps to reduce exposure include:</p>
<ul>
<li>Restrict management and SSL VPN interfaces from direct internet access wherever possible, placing them behind a VPN or allowlist instead.</li>
<li>Apply the latest Fortinet security updates and firmware for your FortiGate devices without delay.</li>
<li>Audit administrator accounts for unexpected additions or changed credentials.</li>
<li>Enable multi-factor authentication for all administrative access.</li>
<li>Review logs for signs of tampering, such as altered configs or unexplained login activity.</li>
</ul>
<p dir="auto">Given that lockouts are the reported outcome, having offline backups of device configurations and a tested recovery plan is worth prioritizing. If you suspect a device has already been compromised, isolating it from the network before attempting remediation helps prevent further unauthorized changes.</p>
<p dir="auto">Source: <a href="https://www.bleepingcomputer.com/news/security/fbi-ongoing-fortibleed-attacks-lock-out-fortigate-vpn-admins" target="_blank" rel="noopener noreferrer nofollow ugc">Unknown</a></p>
<p dir="auto">Has anyone here already reviewed their FortiGate admin access and MFA settings in response to this warning?</p>
]]></description><link>https://xploitlk.com/topic/605/fbi-ongoing-fortibleed-attacks-lock-out-fortigate-vpn-admins</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 07:51:41 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/605.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 07 Oct 2026 22:30:22 GMT</pubDate><ttl>60</ttl></channel></rss>