— Unscored

Fortinet FortiMail Path Traversal Vulnerability

CVE-2026-104286 Exploited

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.

Being exploited in the wild

Catalogued 1 October 2026 · US federal remediation deadline 4 October 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…

Exploit code is also public: Public PoC

Public PoCShadowForge-Cyber/CVE-2026-104286-POC
Public PoCtechupdate24/fortimail-zero-day-cve-2026-104286
Public PoCkh20134/fortimail-cve-2026-104286-response
Public PoCCompleteTech-Security/fortimail-cve-2026-104286-check
Public PoCmaxprog-svg/CVE-2026-104286

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Yes — listed in the CISA KEV catalog
Exploit availability: CISA KEV, Public PoC
Published: 1 October 2026
Last updated: 1 October 2026
Affected: Fortinet · FortiMail
Weakness: CWE-158, CWE-22

At the source

CISA KEV

References

https://www.cisa.gov/known-exploited-vulnerabilities-catalog

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 2? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-104286