CVE
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiMail 8.0.0…
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.4, 7.4.0 through 7.4.6, or 7.2 (all versions). Affected FortiRecorder 7.6.0 through 7.6.2, 7.2.0 through 7.2.12, or 7.0.0 through 7.0.6. Affected FortiVoice 8.0.0 through 8.0.1, 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, or 7.0.0 through 7.0.8.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An authenticated attacker can run unauthorized operating system commands in Fortinet FortiMail, FortiRecorder, and FortiVoice by sending specially crafted HTTP requests. The attack can be launched remotely over the network and needs only low-privilege login.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.4, FortiMail 7.4.0 through 7.4.6, FortiMail 7.2 all versions, FortiRecorder 7.6.0 through 7.6.2, FortiRecorder 7.2.0 through 7.2.12, FortiRecorder 7.0.0 through 7.0.6, FortiVoice 8.0.0 through 8.0.1, FortiVoice 7.4.0 through 7.4.2, FortiVoice 7.2.0 through 7.2.5, FortiVoice 7.0.0 through 7.0.8 may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity8.8/10CVSS 8.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 86 if added to CISA KEV
- Would score about 81 if CISA's SSVC rates exploitation active
- Would score about 43 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.4, 7.4.0 through 7.4.6, or 7.2 (all versions). Affected FortiRecorder 7.6.0 through 7.6.2, 7.2.0 through 7.2.12, or 7.0.0 through 7.0.6. Affected FortiVoice 8.0.0 through 8.0.1, 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, or 7.0.0 through 7.0.8.Workaround: The checked facts do not describe a workaround. Consult Fortinet's advisory for any interim mitigation, and limit access to the affected administrative features until a fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126144 (A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiMail 8.0.0…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126144 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiMail: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.4; from 7.4.0, through 7.4.6; from 7.2.0, through 7.2.9
- Fortinet FortiRecorder: from 7.6.0, through 7.6.2; from 7.2.0, through 7.2.12; from 7.0.0, through 7.0.6
- Fortinet FortiVoice: from 8.0.0, through 8.0.1; from 7.4.0, through 7.4.2; from 7.2.0, through 7.2.5; from 7.0.0, through 7.0.8
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.4, 7.4.0 through 7.4.6, or 7.2 (all versions). (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-196)
- Affected FortiRecorder 7.6.0 through 7.6.2, 7.2.0 through 7.2.12, or 7.0.0 through 7.0.6. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-196)
- Affected FortiVoice 8.0.0 through 8.0.1, 7.4.0 through 7.4.2, 7.2.0 through 7.2.5, or 7.0.0 through 7.0.8. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-196)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126144 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126144 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-196
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126144
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126144"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Fortinet FortiMail
From 8.0.0 · through 8.0.1; From 7.6.0 · through 7.6.4; From 7.4.0 · through 7.4.6; From 7.2.0 · through 7.2.9
- Fortinet FortiRecorder
From 7.6.0 · through 7.6.2; From 7.2.0 · through 7.2.12; From 7.0.0 · through 7.0.6
- Fortinet FortiVoice
From 8.0.0 · through 8.0.1; From 7.4.0 · through 7.4.2; From 7.2.0 · through 7.2.5; From 7.0.0 · through 7.0.8
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126144
Is CVE-2026-126144 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
This is an OS command injection flaw, meaning special characters are not properly neutralized before input reaches a system command. The advisory says an authenticated attacker can execute unauthorized code or commands on the affected appliance.Source: fortiguard.fortinet.com
Which versions are affected by CVE-2026-126144?
FortiMail: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.4; from 7.4.0 through 7.4.6; from 7.2.0 through 7.2.9. FortiRecorder: from 7.6.0 through 7.6.2; from 7.2.0 through 7.2.12; from 7.0.0 through 7.0.6. FortiVoice: from 8.0.0 through 8.0.1; from 7.4.0 through 7.4.2; from 7.2.0 through 7.2.5; from 7.0.0 through 7.0.8.Source: cve.now feed data
Am I affected, and how do I check?
Listed affected versions are FortiMail 8.0.0 to 8.0.1, 7.6.0 to 7.6.4, 7.4.0 to 7.4.6, and 7.2 releases; FortiRecorder 7.6.0 to 7.6.2, 7.2.0 to 7.2.12, and 7.0.0 to 7.0.6; and FortiVoice 8.0.0 to 8.0.1, 7.4.0 to 7.4.2, 7.2.0 to 7.2.5, and 7.0.0 to 7.0.8. To check a device, compare the firmware version shown in its admin interface or system status against these ranges.Source: fortiguard.fortinet.com
How do I fix CVE-2026-126144?
The checked facts do not name a fixed release, so no specific upgrade target can be given. Check Fortinet's advisory for the first fixed version of each affected product line.Source: fortiguard.fortinet.com
What if there's no patch?
The checked facts do not describe a workaround. Consult Fortinet's advisory for any interim mitigation, and limit access to the affected administrative features until a fix is available.Source: fortiguard.fortinet.com