# CVE-2026-126152: CVE-2026-126152

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

A authorization bypass through user-controlled key 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 authenticated remote attacker to delete arbitrary directories as root, or to access or delete other users' calendar and mailbox data across tenant domains, via crafted HTTP requests to the webmail and administrative interfaces.

## 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); ≥ 7.0.0; ≤ 7.0.9 (affected, semver). Source: CNA: fortinet

## Severity and prioritization

- CVSS 3.1: 7.6 (high); CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:L/E:F/RL:O/RC:C; source: CNA: fortinet

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-639

## Exploit evidence

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

## References

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

## Provenance

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

Revision: 3ae947e68e9804c15d46e673af1c431c52501de6ea4dc28d7d24268a58b86ba3

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

## 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.