# CVE-2025-32756: Fortinet Multiple Products Stack-Based Buffer Overflow

> Remote unauthenticated attackers can execute arbitrary code via crafted HTTP requests due to a stack-based buffer overflow in multiple Fortinet products.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:C`)
- **Exploited in the wild:** Yes, since 14 May 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-fcpx-h44g-vx2x

## What is CVE-2025-32756?

CVE-2025-32756 is a critical memory corruption vulnerability in Fortinet FortiCamera, published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-32756?

It affects 5 products.


Products: Fortinet Forticamera Firmware, Fortinet Fortimail, Fortinet Fortindr, Fortinet Fortirecorder, Fortinet Fortivoice.

## How do I fix CVE-2025-32756?

No fix has been published for CVE-2025-32756 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 4 Jun 2025.

## Is CVE-2025-32756 being exploited?

Yes. Attackers have exploited CVE-2025-32756 in the wild since at least 14 May 2025.

Public exploit code:

- Proof of Concept for CVE-2025-32756 - A critical stack-based buffer overflow vulnerability affecting multiple Fortinet products. (github_poc): https://github.com/kn0x0x/CVE-2025-32756-POC
- Designed for Demonstration of Deep Exploitation. (github_poc): https://github.com/exfil0/CVE-2025-32756-POC
- https://github.com/alm6no5/CVE-2025-32756-POC (github_poc): https://github.com/alm6no5/CVE-2025-32756-POC
- CVE-2025-32756: NSE Scanning for RCE in vulnerable FortiVoice, FortiMail, FortiNDR, FortiRecorder and FortiCamera nodes (github_poc): https://github.com/becrevex/CVE-2025-32756
- https://github.com/shan0ar/cve-2025-32756 (github_poc): https://github.com/shan0ar/cve-2025-32756

## Other vulnerabilities in Fortinet FortiCamera

- [CVE-2024-40588](https://insights.sbomify.com/CVE-2024-40588/): Path traversal in FortiCamera (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32756 and fix it if it is affected.

What it is: CVE-2025-32756 is a critical memory corruption vulnerability in Fortinet FortiCamera, published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-32756 in the wild since at least 14 May 2025.

Affected product: Fortinet FortiCamera. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32756/ (Markdown: https://insights.sbomify.com/CVE-2025-32756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32756
- OSV: https://osv.dev/vulnerability/CVE-2025-32756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32756/
Summaries are generated and may contain mistakes; the official description above is the record.