CVE-2026-126263 is an SQL injection flaw in FortiMail. Fortinet says the issue can allow unauthorized code or command execution and rates the vulnerability Critical.Fortinet assigns CVSS 3.1 score 9.4, Critical. The company published FG-IR-26-277 on November 10, 2026.
What it allows
What Is the Impact of CVE-2026-126263?
Fortinet’s summary says the attacker must log in. The same advisory labels the attack unauthenticated. The Fortinet CVSS vector in NVD says the attacker needs no privileges.
The sources disagree about who can reach the flaw. Patch affected hosts based on their build. Treat the login requirement as unresolved.
What Is Known About Exploitation of the FortiMail SQL Flaw?
Fortinet marked Known Exploited as No in FG-IR-26-277. CVE-2026-126263 was absent from CISA KEV catalog version 2026.11.10, released November 10, 2026.
See the separate FortiMail file-write advisory for related coverage. Use the vulnerability management guide to track upgrades and verify them after deployment.
Who is affected
Which Releases Are Affected by CVE-2026-126263?
Fortinet lists three affected lines for systems you run yourself. Find your current build in the affected range. Use the fix column to pick the build to move to.
| Product and release line | Affected releases | Fortinet solution |
|---|---|---|
| FortiMail 8.0 | 8.0.0 through 8.0.1 | Upgrade to 8.0.2 or above |
| FortiMail 7.6 | 7.6.0 through 7.6.4 | Upgrade to 7.6.7 or above |
| FortiMail 7.4 | 7.4.0 through 7.4.6 | Upgrade to 7.4.7 or above |
Fortinet says it updated FortiMail Cloud to 7.6.7 GA or 8.0.2 GA. The advisory says that FortiMail Cloud customers need take no action for this CVE.
Fortinet lists no virtual patch. Self-managed deployments should follow the upgrade guidance in the table for the installed release line.
Check FG-IR-26-277 before scheduling maintenance. The patch management glossary describes the process of applying and verifying fixes.
Timeline
- 2026-11-10
Fortinet published FG-IR-26-277 and marked Known Exploited as No.
- 2026-11-11
The CVE Program and NVD published the CVE-2026-126263 records attributed to Fortinet.
What to do
-
Confirm the deployment type and release
Inventory FortiMail appliances and distinguish them from FortiMail Cloud. Compare each self-managed release with FG-IR-26-277.
-
Follow the vendor upgrade target
Upgrade affected 8.0 to 8.0.2 or above, 7.6 to 7.6.7 or above, and 7.4 to 7.4.7 or above.
-
Verify the upgrade
Confirm the fixed release after maintenance and verify routine mail processing. Recheck FG-IR-26-277 for any clarification of authentication requirements.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-126263 in Brandefense Atlas
The Atlas record of CVE-2026-126263: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-126263 require authentication?
Fortinet’s summary says authenticated, while its attack-type label says unauthenticated and its NVD vector lists no required privileges. Treat the requirement as unresolved and apply the vendor fix.
Which FortiMail releases are affected?
Fortinet lists 8.0.0 through 8.0.1, 7.6.0 through 7.6.4, and 7.4.0 through 7.4.6.
Do FortiMail Cloud customers need to upgrade?
Fortinet says the cloud service has been updated to 7.6.7 GA or 8.0.2 GA and customers need take no action for this issue.
Is CVE-2026-126263 listed as exploited?
Fortinet marked Known Exploited as No in FG-IR-26-277. CVE-2026-126263 was absent from CISA KEV catalog version 2026.11.10, released November 10, 2026.
Sources
- FG-IR-26-277 Fortinet security advisoryFortinet PSIRT
- CVE-2026-126263 Fortinet CNA recordCVE Program
- CVE-2026-126263National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency