CVE-2025-32756 · Published 13 May 2025
Fortinet Multiple Products
On CISA's KEV list one day after disclosure; 6 public exploits.
Fortinet FortiFone, FortiVoice, FortiNDR and FortiMail contain a stack-based overflow vulnerability that may allow a remote unauthenticated attacker to execute arbitrary code or commands via crafted HTTP requests.
CISA required action (federal due date 4 Jun 2025): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 14 May 2025, due 4 Jun 2025
- EPSS, 30-day forecast
- 31%, 98th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 13 May 2025 to today
- Disclosed
- KEV+1 d
- First PoC+4 d
4 days from the KEV listing to the first proof of concept
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 6 known · links only
GitHub PoCs 6Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars6
- kn0x0x/CVE-2025-32756-POCTrust ok 100191 stars
Proof of Concept for CVE-2025-32756 - A critical stack-based buffer overflow vulnerability affecting multiple Fortinet products.
created 5 Jun 2025
- exfil0/CVE-2025-32756-POCTrust ok 1004 stars
Designed for Demonstration of Deep Exploitation.
created 18 May 2025
- alm6no5/CVE-2025-32756-POCTrust ok 1000 stars
created 9 Jun 2025
- becrevex/CVE-2025-32756Trust ok 1000 stars
CVE-2025-32756: NSE Scanning for RCE in vulnerable FortiVoice, FortiMail, FortiNDR, FortiRecorder and FortiCamera nodes
created 9 Jun 2025
- shan0ar/cve-2025-32756Trust ok 1000 stars
created 23 Jul 2025
- B1ack4sh/Blackash-CVE-2025-32756Not checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.