# CVE-2026-126147: CVE-2026-126147

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through 7.4.8, FortiMail 7.2 all versions may allow an unauthenticated attacker to execute unauthorized code or commands via crafted requests.

## Remediation

- fix: Upgrade to FortiMail version 8.0.2 or above
Upgrade to FortiMail version 7.6.7 or above
Upgrade to FortiMail version 7.4.9 or above (source: CNA: fortinet)

## Affected products and versions

- Fortinet / FortiMail: ≥ 8.0.0; ≤ 8.0.1 (affected, semver); ≥ 7.6.0; ≤ 7.6.6 (affected, semver); ≥ 7.4.0; ≤ 7.4.8 (affected, semver); ≥ 7.2.0; ≤ 7.2.9 (affected, semver). Source: CNA: fortinet

## Severity and prioritization

- CVSS 3.1: 9.8 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:R; source: CNA: fortinet

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-22

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://fortiguard.fortinet.com/psirt/FG-IR-26-199 (CNA: fortinet)

## Provenance

- CNA: fortinet: https://www.cve.org/CVERecord?id=CVE-2026-126147; retrieved 2026-11-11; source updated 2026-11-11

Revision: 876d6063c313526602581031454423a64ebe5d48c9643f1eed3256fc51325785

Canonical: https://y2.dev/cve/CVE-2026-126147

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.