CISA Issues Urgent Advisory as 'FortiBleed' Campaign Compromises Over 86,000 Fortinet Devices Globally

FortiBleed Carnage: 86,000+ Fortinet Devices Exposed in Massive Credential Leak

CRITICAL
June 20, 2026
June 22, 2026
6m read
Data BreachThreat ActorCyberattack

Impact Scope

People Affected

Administrators of over 86,000 devices

Industries Affected

TelecommunicationsGovernmentEducationFinanceHealthcareManufacturingCritical Infrastructure

Geographic Impact

IndiaUnited StatesMexicoColombiaThailand (global)

Related Entities(initial)

Threat Actors

Unnamed Russian-speaking threat group

Products & Tech

FortiGateHashtopolisActive Directory

Other

ChiselNeo-reGeorg

Full Report(when first published)

Executive Summary

A large-scale credential theft campaign, publicly tracked as FortiBleed, has resulted in the compromise of at least 86,000 Fortinet FortiGate firewalls and SSL VPN gateways across 194 countries. The incident, attributed to a Russian-speaking threat actor, does not leverage a new vulnerability but rather capitalizes on poor credential hygiene and legacy password hashing mechanisms. The threat actor amassed credentials from various sources, including previous data breaches and infostealer malware logs, and successfully cracked them to gain unauthorized access. In response, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent advisory directing organizations to immediately harden their Fortinet appliances by rotating all credentials, enabling MFA, and auditing for lateral movement.

Threat Overview

The FortiBleed campaign represents a significant threat to organizations relying on Fortinet security appliances. The core of the attack is a massive credential stuffing and cracking operation. Threat actors collected a large dataset of credentials associated with FortiGate devices and utilized a 45-GPU cluster managed with the Hashtopolis tool to crack password hashes. The success of this campaign is largely attributed to two factors: the use of weak or default passwords by administrators and the exploitation of older, less secure hashing algorithms previously used in FortiGate configuration files.

Once valid credentials were obtained, the attackers gained access to the SSL VPN and administrative interfaces of the firewalls. This initial foothold was then used to deploy post-exploitation tools like Chisel and Neo-reGeorg for tunneling traffic and facilitating lateral movement into the internal corporate networks. The most affected sectors include telecommunications, government, and education, with a high concentration of compromised devices in India, the U.S., Mexico, Colombia, and Thailand.

Technical Analysis

The attack chain is straightforward but highly effective, relying on operational security failures rather than sophisticated exploits.

  1. Credential Acquisition: The threat actor gathered credentials from publicly available data breaches and underground marketplaces where logs from infostealer malware are sold.
  2. Password Cracking: The attackers targeted SSL VPN authentication hashes. Using a powerful GPU cluster, they brute-forced these hashes to recover plaintext passwords. The success rate was high due to the use of weak hashing algorithms in older FortiOS versions and users choosing simple, guessable passwords.
  3. Initial Access: Armed with valid credentials, the attackers logged into the FortiGate SSL VPN portals. According to analysis from SOCRadar, 35% of the compromised accounts were generic 'admin' accounts, and 28.3% were other built-in system accounts, indicating a widespread failure to change default settings. This aligns with MITRE ATT&CK T1078 - Valid Accounts.
  4. Post-Exploitation: After gaining access, attackers were observed using tunneling tools like Chisel and Neo-reGeorg to establish persistent access and pivot into the internal network. This corresponds to T1572 - Protocol Tunneling. This allows them to bypass perimeter defenses and move laterally, as described in T1021 - Remote Services.

The core issue is the historical use of weaker hashing mechanisms for credentials in FortiGate configuration files. While newer versions use PBKDF2, many devices may still have accounts with legacy hashes if they were created on older firmware and never updated.

Impact Assessment

The business impact of a compromised edge security appliance is severe. Attackers with administrative access to a FortiGate firewall can:

  • Decrypt and monitor all network traffic passing through the device.
  • Disable security policies to allow malicious traffic into the network.
  • Create VPN tunnels to exfiltrate sensitive data or establish a covert command-and-control channel.
  • Use the firewall as a pivot point to launch attacks against internal assets, including domain controllers and critical servers.
  • Deploy ransomware across the entire network.

The reputational damage and regulatory fines resulting from a data breach originating from this vector can be substantial. The cost of incident response, forensic analysis, and remediation adds significant financial strain.

IOCs — Directly from Articles

No specific file hashes, IP addresses, or domains were provided in the source articles.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns which could indicate related activity:

Type
process_name
Value
chisel
Description
The Chisel tunneling tool process, often seen in post-exploitation.
Type
process_name
Value
neoregeorg
Description
The Neo-reGeorg tunneling tool, used for creating SOCKS proxies.
Type
log_source
Value
FortiGate Event Logs
Description
Monitor for event IDs related to failed and successful administrative logins from unusual IP addresses or geolocations.
Type
network_traffic_pattern
Value
Unusual outbound connections from Firewall Mgmt Interface
Description
The management interface should typically only communicate with internal administrative subnets.
Type
command_line_pattern
Value
diagnose sys session list
Description
Attackers may use this command to view active sessions. Monitor for its use by non-standard admin accounts.

Detection & Response

Detection:

  • Log Analysis: Ingest FortiGate event logs into a SIEM. Create alerts for multiple failed login attempts followed by a success from the same IP address. Monitor for logins from geographically impossible locations or non-standard user agents. D3FEND's Domain Account Monitoring (D3-DAM) is relevant here.
  • Network Traffic Analysis: Monitor traffic originating from the firewall's management interface. Any connections to external, non-Fortinet IP addresses are highly suspicious. D3FEND's Network Traffic Analysis (D3-NTA) can help identify anomalous patterns.
  • Configuration Auditing: Regularly audit FortiGate configurations for legacy user accounts, accounts with weak passwords, and overly permissive firewall rules.

Response:

  1. Immediately terminate all active SSL VPN and administrative sessions.
  2. Isolate potentially compromised devices from the network to prevent further lateral movement.
  3. Preserve logs and a snapshot of the device for forensic analysis.
  4. Reset passwords for ALL administrative and SSL VPN user accounts, enforcing a strong complexity policy.
  5. Begin a hunt for signs of lateral movement within the internal network, looking for the use of tools like Chisel or unusual activity from service accounts.

Mitigation

Immediate Actions:

  • Rotate All Credentials: Immediately reset all local user, administrator, and VPN user passwords on all Fortinet devices.
  • Enable MFA: Enforce phishing-resistant Multi-factor Authentication (M1032) for all administrative and VPN accounts. This is the single most effective mitigation.
  • Restrict Access: Apply the principle of least privilege. Restrict access to the SSL VPN and administrative interfaces to trusted IP address ranges. Do not expose management interfaces to the public internet. This aligns with M1035 - Limit Access to Resource Over Network.

Strategic Improvements:

  • Credential Hygiene: Implement and enforce a strong password policy. Eliminate default accounts like 'admin' and use named administrator accounts. This is a key part of M1026 - Privileged Account Management.
  • Update Hashing Algorithm: Ensure all administrator credentials are being stored using PBKDF2. This can be verified with the command show system admin. If any accounts are using the legacy format, they must be reset.
  • Regular Auditing: Implement a regular schedule for auditing firewall rules, user accounts, and device configurations. This falls under M1047 - Audit.

Timeline of Events

1
June 18, 2026
CISA issues an urgent advisory regarding the FortiBleed campaign.
2
June 19, 2026
Multiple security news outlets report on the scale of the compromise, with figures ranging from 74,000 to over 86,000 devices.
3
June 20, 2026
This article was published

Article Updates

June 22, 2026

International agencies issue joint alert on FortiBleed, reinforcing threat and detailing credential stuffing TTPs.

MITRE ATT&CK Mitigations

Enforcing MFA on all administrative and VPN accounts is the most critical defense against credential-based attacks.

Mapped D3FEND Techniques:

Enforce strong, complex passwords and prevent reuse to make cracking and guessing more difficult.

Mapped D3FEND Techniques:

Regularly audit and remove default, unused, or shared privileged accounts.

Mapped D3FEND Techniques:

Restrict management interface access to a dedicated, internal administrative network.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Implement comprehensive logging and regular auditing of administrative activities on network devices.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

Immediately enforce phishing-resistant Multi-Factor Authentication for all administrative and SSL-VPN user access on FortiGate devices. This is the single most effective countermeasure against the FortiBleed campaign, as it invalidates stolen credentials alone. Prioritize hardware tokens (FIDO2/WebAuthn) or certificate-based authentication over less secure methods like SMS or push notifications, which are susceptible to MFA fatigue attacks. For administrative access, MFA should be required for both GUI and CLI sessions. For SSL-VPN users, ensure that all user groups, including third-party contractors and partners, are enrolled. This action directly hardens the initial access vector used by the threat actors and serves as a powerful compensating control even if password hygiene is poor. The implementation should be coupled with user training to ensure smooth adoption and awareness of MFA-related social engineering tactics.

Implement and enforce a robust password policy for all FortiGate local user accounts. This policy should mandate a minimum length of 15 characters, including a mix of uppercase letters, lowercase letters, numbers, and special characters. Critically, disable or remove all default accounts (e.g., 'admin') and replace them with named administrator accounts. Configure the device to enforce password history to prevent reuse and set a maximum password age of 90 days. Forcing a password change for all users immediately will invalidate any currently compromised credentials. This D3FEND technique directly addresses the root cause of the FortiBleed campaign's success: weak, default, and easily crackable passwords. Use FortiGate's built-in password policy enforcement features to automate this control.

Isolate the FortiGate management interfaces (both HTTPS and SSH) from the public internet and general corporate user networks. Create a dedicated, segmented management VLAN or subnet accessible only from a limited set of hardened administrative workstations or a bastion host. Use firewall rules on the FortiGate itself ('Local-in Policy') to strictly control which source IPs can connect to the management ports. This practice of network isolation drastically reduces the attack surface, making it impossible for external attackers to even attempt to log in, regardless of whether they have valid credentials. This directly counters the initial access phase of the FortiBleed attack and is a foundational security best practice for all network infrastructure.

Timeline of Events

1
June 18, 2026

CISA issues an urgent advisory regarding the FortiBleed campaign.

2
June 19, 2026

Multiple security news outlets report on the scale of the compromise, with figures ranging from 74,000 to over 86,000 devices.

Sources & References(when first published)

CISA warns Fortinet users to secure devices after FortiBleed leak
BleepingComputer (bleepingcomputer.com) June 19, 2026
FortiBleed: 86,000 Fortinet Device Credentials Compromised
SecurityWeek (securityweek.com) June 19, 2026
CISA Warns Fortinet Customers as FortiBleed Hits 86,644 FortiGate Devices
The Hacker News (thehackernews.com) June 19, 2026
FortiBleed Campaign Exposing Credentials for 73,932 FortiGate Systems
Recorded Future (recordedfuture.com) June 19, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

FortiBleedCredential StuffingPassword CrackingFortinetCISAVPN SecurityMFA

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.