CVE-2026-21643
An authority record changed. This is a change in what is asserted about exploitation, not in how the vulnerability is described.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- CISA requires: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. The federal deadline has passed: overdue since 2026-04-16. CISA KEVCISA's notes for this entry: fortiguard.fortinet.com
- No fix version is held. CISA's required action above is the reference.
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiClientEMS 7.4.4 may allow an unauthenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.
- weakness
- CWE-89 Execute unauthorized code or commands
- affected
- Fortinet FortiClientEMS
- published ranges
- fortinet forticlientems 7.4.4
- fixed in
- No fix version in held sources.
- severity
- 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
- assigned by
- fortinet
- published
- 2026-02-06
check us fortiguard.fortinet.com
Authority held, dated
- CISA KEV
- listed
- added
- 2026-04-13
- remediation due
- 2026-04-16
- ransomware use
- unknown
- remediation status
- overdue since 2026-04-16
- exploit code
- 2 public proof-of-concept repositories, first seen 2026-03-27 (PoC-in-GitHub).
A KEV listing is an assertion of observed exploitation. It is the only element on this page that makes that claim.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 6 Feb 2026 | 0.00129 | |
| 12 Feb 2026 | 0.00169 | |
| 18 Feb 2026 | 0.00029 | |
| 6 Mar 2026 | 0.0003 | |
| 10 Apr 2026 | 0.13698 | crossed 0.10 |
| 7 May 2026 | 0.62516 | crossed 0.50 |
| 10 Jun 2026 | 0.70889 | |
| 15 Jun 2026 | 0.94085 | crossed 0.90 · scoring model v2026.06.15 |
| 28 Sep 2026 | 0.93723 | |
| 4 Oct 2026 | 0.93871 |
23 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Listed, added 2026-04-13. Due 2026-04-16. A changed deadline or a change in ransomware use changes this brief.
- exploit probability
- 0.94 on 2026-10-04 (FIRST's EPSS, a probability and not evidence of exploitation). It is above the top band line, 90%.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-21643', '2026-10-31T23:59:59.999999Z', now());