Skip to content
Server Security Center
KEVhigh7.4

CVE-2025-25249: Fortinet Multiple Products Heap-based Buffer Overflow

Fortinet Multiple Products · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-09.

CVSS v3.1 (CVE record)
7.4
high
EPSS (exploit probability, 30 days)
3.7%
higher than 90.1% of all CVEs
Added to CISA KEV
2026-09-09
US federal due date 2026-09-12
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-25249 explained

CVE-2025-25249 is a heap-based buffer overflow in Fortinet FortiOS and FortiSwitchManager. Specially crafted packets can let an attacker execute unauthorized code or commands on the device. CISA lists it as known to be exploited, so affected network devices need prompt attention.

Impact

An unauthenticated attacker with network access can send specially crafted packets to run unauthorized code or commands. No user interaction is needed, but attack complexity is high. Success brings high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation is not expected to scale without manual steps. CISA lists it as known to be exploited.

Who is affected

The CVE record lists FortiSwitchManager ≥ 7.2.2, ≤ 7.2.5, fixed in 7.0.6 and 7.2.7. For FortiOS it lists ≥ 7.2.4, ≤ 7.2.11, ≥ 7.4.0, ≤ 7.4.7 and ≥ 7.6.0, ≤ 7.6.2, fixed in 7.0.18, 7.2.12, 7.4.9 and 7.6.4; 8.0.0 is announced as upcoming. The description names a wider set, including FortiOS 7.0.0 through 7.0.17 and FortiOS 6.4 all versions.

Written with AI from the data on this page and checked against it automatically.

Official description

A heap-based buffer overflow vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.8, FortiOS 7.2.0 through 7.2.11, FortiOS 7.0.0 through 7.0.17, FortiOS 6.4 all versions, FortiSwitchManager 7.2.0 through 7.2.6, FortiSwitchManager 7.0.0 through 7.0.5 allows attacker to execute unauthorized code or commands via specially crafted packets

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Fortinet FortiSwitchManager
    Affected
    • ≥ 7.2.2, ≤ 7.2.5
    Fixed in
    • 7.0.6
    • 7.2.7

    Fixed versions taken from the CNA solution text.

  • Fortinet FortiOS
    Affected
    • ≥ 7.2.4, ≤ 7.2.11
    • ≥ 7.4.0, ≤ 7.4.7
    • ≥ 7.6.0, ≤ 7.6.2
    Fixed in
    • 7.0.18
    • 7.2.12
    • 7.4.9
    • 7.6.4
    • 8.0.0 (upcoming)

    Fixed versions taken from the CNA solution text.

Also affected (reported by product suppliers)

  • Siemens RUGGEDCOM APE1808
    Affected
    • all versions
    Fixed in
    not stated

How to fix it

  • Update to the fixed version for your product:
    • Fortinet FortiSwitchManager: 7.0.6, 7.2.7
    • Fortinet FortiOS: 7.0.18, 7.2.12, 7.4.9, 7.6.4, 8.0.0 (upcoming)
  • Vendor advisory: fortiguard.fortinet.com/psirt/FG-IR-25-084
  • CISA's deadline for US federal agencies: 2026-09-12 (passed) – a useful benchmark for everyone else, too.

Vendor solution:

  • Upgrade to FortiSwitchManager version 7.2.7 or above
  • Upgrade to FortiSwitchManager version 7.0.6 or above Fortinet remediated this issue in FortiSASE version 25.2.c and hence customers do not need to perform any action.
  • Fortinet remediated this issue in FortiSASE version 25.1.b and hence customers do not need to perform any action.
  • Upgrade to upcoming FortiOS version 8.0.0 or above
  • Upgrade to FortiOS version 7.6.4 or above
  • Upgrade to FortiOS version 7.4.9 or above
  • Upgrade to FortiOS version 7.2.12 or above
  • Upgrade to FortiOS version 7.0.18 or above

What to do

  1. Upgrade FortiOS to 7.0.18, 7.2.12, 7.4.9 or 7.6.4, matching your release line.
  2. Upgrade FortiSwitchManager to 7.0.6 or 7.2.7, matching your release line.
  3. Follow the Fortinet advisory and apply its mitigations on any device you cannot upgrade immediately.
  4. Restrict network exposure of affected devices, especially management interfaces reachable from the internet.
  5. Check affected devices for signs of compromise, as CISA lists the vulnerability as known to be exploited.
  6. If mitigations are unavailable, follow CISA's required action, which includes discontinuing use of the product.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-122 Execute unauthorized code or commands

Questions about CVE-2025-25249

Is CVE-2025-25249 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-09, with a US federal due date of 2026-09-12. Whether it is used in ransomware campaigns is listed as unknown.
Does an attacker need credentials?
No. The CVSS data shows no privileges and no user interaction are required, and the attack works over the network. Attack complexity is rated high.
Are FortiOS 6.4 devices affected?
The description names FortiOS 6.4 all versions as affected, but the CVE record lists no fixed version for it. Check the Fortinet advisory for guidance on those devices.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.