CVE-2026-25089 · Published 9 Jun 2026
Fortinet FortiSandbox
On CISA's KEV list 37 days after disclosure; 4 public exploits.
Fortinet FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS contain an OS command injection vulnerability that allows an unauthenticated attacker to execute unauthorized commands via specifically crafted HTTP requests.
CISA required action (federal due date 19 Jul 2026): Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
Signals
- KEV, exploited in the wild
- yes, added 16 Jul 2026, due 19 Jul 2026
- EPSS, 30-day forecast
- 76%, 100th 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 9 Jun 2026 to today
- Disclosed
- First PoC+1 d
- KEV+36 d
36 days from the first proof of concept to the KEV listing
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 4 known · links only
GitHub PoCs 4Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars4
- HORKimhab/CVE-2026-25089Trust ok 1006 stars
CVE-2026-25089 - Fortinet FortiSandbox
created 10 Jun 2026
- 0xBlackash/CVE-2026-25089Trust ok 1003 stars
CVE-2026-25089
created 12 Jun 2026
- 0xredash/CVE-2026-25089Trust ok 1003 stars
CVE-2026-25089
created 12 Jun 2026
- ashrafzaryouh/CVE-2026-25089Not checked3 stars
CVE-2026-25089
created 12 Jun 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.