CVE-2026-126159 · Infrastructure
NO FIX YET · SEE WHAT TO DO
FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and all of 7.2 let an unauthenticated attacker send a crafted quarantine release request. The attacker can release or delete quarantined messages belonging to arbitrary mailboxes.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Organizations running a FortiMail email gateway in the affected version ranges, where the quarantine interface is reachable by an attacker. The sources do not state whether a non-default setting is required, so the exposure of appliances behind a private network is unknown. Teams on other FortiMail versions or without FortiMail can skip it.
Not affected if version-outside-range
Who cares email-gateway, fortimail, fortinet
get system status on the CLI, and compare it with the affected ranges.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.