Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE reserved
- CVE publishedsame day
- First KEV listingsame day
- Last sightingsame day
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Oct 1, 2026
- EUVDENISA, European Unionlisted Oct 1, 2026
- VulnCheck KEVcommercial researchlisted Oct 1, 2026
- CIRCLaggregator, mirrors the abovelisted Oct 1, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationfortiguard.fortinet.com/psirt/FG-IR-26-175
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
2 public reports collected from VulnCheck and CIRCL, first on Oct 1, 2026. Each links to its original source. We have not verified them.
Description
Fortinet FortiMail contains a path traversal and an improper neutralization of NULL byte or NULL character vulnerability that may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests.
Required action (CISA)
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.




