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
- Fixed in 8.0.2
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 8.0.2.
- 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? →
- 29/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
A command injection flaw in Fortinet FortiMail lets an authenticated administrator run unauthorized code or commands as root through specially crafted HTTP requests. The attacker can reach the bug remotely over the network, but they must have administrator-level credentials to do so.
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 may allow an authenticated administrator to execute unauthorized code or commands as root via specially 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)
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 36 if CISA's SSVC rates it automatable
What to do
Upgrade to a fixed version: 8.0.2.
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-126158 (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-126158 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiMail: from 8.0.0, through 8.0.1
Fixed versions: 8.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126158 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126158 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-210
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-126158
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-126158"}.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
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-126158
Is CVE-2026-126158 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?
An input-handling flaw lets special characters pass into operating system commands on FortiMail. An attacker who can reach the affected feature could run unauthorized code or commands as root on the FortiMail system.Source: fortiguard.fortinet.com
Which versions are affected by CVE-2026-126158?
FortiMail: from 8.0.0 through 8.0.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions 8.0.0 through 8.0.1 of Fortinet FortiMail are listed as affected, with no extra conditions given. To check a system, look at the firmware version shown on the FortiMail admin dashboard or in the system status output.Source: fortiguard.fortinet.com
How do I fix CVE-2026-126158?
Upgrade FortiMail to version 8.0.2 or above, which is the listed fix. No workaround is given in the facts.Source: fortiguard.fortinet.com