# CVE-2026-126159: CVE-2026-126159

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 unauthenticated attacker to release or delete quarantined messages for arbitrary mailboxes via a crafted quarantine release request.

## 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: 7.5 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/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-211 (CNA: fortinet)

## Provenance

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

Revision: b2f355542c667a54f9dc47ff68d4aea1111465f5affd76654b911ad5bb5c6be1

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

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