dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Jun 2025.
FortimailApplication · Fortinet

CVE-2025-32756

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 6.4.6 / 6.4.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stack-based buffer overflow vulnerability [CWE-121] vulnerability in Fortinet FortiCamera 2.1.0 through 2.1.3, FortiCamera 2.0 all versions, FortiCamera 1.1 all versions, FortiMail 7.6.0 through 7.6.2, FortiMail 7.4.0 through 7.4.4, FortiMail 7.2.0 through 7.2.7, FortiMail 7.0.0 through 7.0.8, FortiNDR 7.6.0, FortiNDR 7.4.0 through 7.4.7, FortiNDR 7.2.0 through 7.2.4, FortiNDR 7.0.0 through 7.0.6, FortiRecorder 7.2.0 through 7.2.3, FortiRecorder 7.0.0 through 7.0.5, FortiRecorder 6.4.0 through 6.4.5, FortiVoice 7.2.0, FortiVoice 7.0.0 through 7.0.6, FortiVoice 6.4.0 through 6.4.10 allows a remote unauthenticated attacker to execute arbitrary code or commands via sending HTTP requests with specially crafted hash cookie.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in multiple Fortinet products (FortiCamera, FortiMail, FortiNDR, FortiRecorder, FortiVoice) where processing a specially crafted hash cookie in HTTP requests overflows a fixed-size buffer on the stack, allowing an attacker to overwrite return addresses and execute arbitrary code.

MitigationApply vendor-supplied patches to upgrade affected products to the latest fixed versions. If patching is not immediately possible, consider restricting network access to management interfaces or implementing web application firewall rules to detect abnormal hash cookie patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortimailApplication
Affected:>= 7.0.0, < 7.0.9>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.5>= 7.6.0, < 7.6.3
FortindrApplication
Affected:>= 7.0.0, < 7.0.7>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.8= 1.1.0= 1.2.0= 1.3.0= 1.4.0= 1.5.0= 7.1.0= 7.1.1= 7.6.0
FortirecorderApplication
Affected:>= 6.4.0, < 6.4.6>= 7.0.0, < 7.0.6>= 7.2.0, < 7.2.4
FortivoiceApplication
Affected:>= 6.4.0, < 6.4.11>= 7.0.0, < 7.0.7= 7.2.0
Forticamera FirmwareOperating system
Affected:>= 2.0.0, <= 2.1.3>= 1.1.0, <= 1.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Fortinet product
    Access the device administrative interface or use the command line (e.g., 'get system status' on FortiGate-based products) to determine the exact product name running in your environment.
    Affected if The product is FortiMail, FortiNDR, FortiRecorder, FortiVoice, or FortiCamera.
  2. Determine the installed version
    Run 'get system status' or navigate to System > Settings > Firmware in the web UI to retrieve the exact firmware version number.
    Affected if The version falls within any of the affected ranges: FortiMail 7.0.0-7.0.8, 7.2.0-7.2.7, 7.4.0-7.4.4, or 7.6.0-7.6.2; FortiNDR 7.0.0-7.0.6, 7.2.0-7.2.4, 7.4.0-7.4.7, or specific point versions 1.1.0-1.5.0, 7.1.0-7.1.1, 7.6.0; FortiRecorder 6.4.0-6.4.5, 7.0.0-7.0.5, 7.2.0-7.2.3; FortiVoice 6.4.0-6.4.
  3. Verify HTTP service is exposed
    Check network configuration or run 'show system interface' to confirm that HTTP management or web UI is enabled and accessible over the network.
    Affected if HTTP or HTTPS web interface is enabled and reachable from network segments accessible to attackers.
  4. Inspect for suspicious cookie processing
    Review HTTP access logs (typically located in /var/log/httpd or /var/log/nginx, or via the web UI log viewer) for requests containing unusually long or malformed 'hash' cookie values.
    Affected if HTTP requests with oversized or specially crafted hash cookies are being processed by the affected service.

Your environment is affected if you are running any of the listed Fortinet products within the specified version ranges and the HTTP web interface is exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.4.6 / 6.4.11 / 7.0.6 or later
Fixed in 6.4.66.4.117.0.6
Interim mitigation

Apply vendor-supplied patches to upgrade affected products to the latest fixed versions. If patching is not immediately possible, consider restricting network access to management interfaces or implementing web application firewall rules to detect abnormal hash cookie patterns.

Recommended fix High confidence

FortiMail: 7.0.9/7.2.8/7.4.5/7.6.3 | FortiNDR: 7.0.7/7.2.5/7.4.8 | FortiRecorder: 6.4.6/7.0.6/7.2.4 | FortiVoice: 6.4.11/7.0.7/latest 7.2.x | FortiCamera: latest available (newer than 2.1.3/1.1.5)

  1. 1. Identify the exact FortiMail, FortiNDR, FortiRecorder, FortiVoice, or FortiCamera model and current firmware version installed.
  2. 2. Navigate to the Fortinet FortiGuard portal at https://www.fortiguard.com/ to obtain the official firmware releases for your product.
  3. 3. Download the appropriate fixed firmware version based on your product: For FortiMail upgrade to 7.0.9, 7.2.8, 7.4.5, or 7.6.3; For FortiNDR upgrade to 7.0.7, 7.2.5, 7.4.8; For FortiRecorder upgrade to 6.4.6, 7.0.6, or 7.2.4; For FortiVoice upgrade to 6.4.11, 7.0.7, or the latest 7.2.x version; For FortiCamera upgrade to the latest available firmware (newer than 2.1.3 or 1.1.5).
  4. 4. Review Fortinet release notes for any special migration or upgrade prerequisites.
  5. 5. Backup current configuration before applying the firmware upgrade.
  6. 6. Apply the firmware upgrade via the product's web UI or CLI following standard Fortinet upgrade procedures.
  7. 7. After upgrade, verify the firmware version matches the fixed release and confirm the vulnerability is resolved.
Caveat Review Fortinet release notes for any configuration or feature changes between your current version and the target fixed version before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortimail Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32756 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32756 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data