DaystoPatch

FortinetExploited incident

FortiClient EMS 7.4.4 unauthenticated SQL injection in the administrative interface

CVE-2026-21643Critical, CVSS 9.8In CISA's Known Exploited Vulnerabilities catalog since 13 Apr 2026

  • Exploited after a fix existed
FixedFixed for every supported version on the day it became public.

Response

Silence
same day
First public report to first vendor statementUnverified source
Exposure
same day
First public report to first fixUnverified source
Follow-through
same day
First public report to a fix for every supported versionUnverified source
  • Vendor silent
  • Vendor statement, no fix
  • Fixed for some versions
  • Fixed when disclosed
  • Date only, no time of day

Timeline and evidence

Open a moment to see its source and archived quote.

  1. First public report

    date onlyUnverified: no archived copy, quote not checked yet

    Fortinet PSIRT FG-IR-25-1142CuratedQuote not checked yet

    2026-02-06: Initial publication

    Internally discovered; the advisory (with the fix) is the first public signal.

    Source
    Fortinet PSIRT FG-IR-25-1142 vendor advisory
    Recorded time
    Precision
    Date only (no time of day is shown)
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Not checked yet
    Snapshot
    No archived snapshot
    Used in metrics
    Yes
    Dispute this timestamp
    4 more sources for this moment
    CVE.org record CVE-2026-21643ClaimedQuote verified6 Feb 2026, 08:24 UTC

    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

    CVE record published.

    Recorded time
    Precision
    To the minute
    Origin
    Claimed. The date the source gives.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:ff6ff84a2e1ed55e…
    Used in metrics
    No, kept for the record
    Dispute this timestamp
    Bluesky postClaimedQuote not checked yet6 Feb 2026, 10:00 UTC

    🔴 CVE-2026-21643 - Critical (9.8)

    Earliest third-party post we hold.

    Source
    Bluesky post social
    Recorded time
    Precision
    To the minute
    Origin
    Claimed. The date the source gives.
    Quote check
    Not checked yet
    Snapshot
    No archived snapshot
    Used in metrics
    No, kept for the record
    Dispute this timestamp
    Mastodon postClaimedQuote not checked yet13 Feb 2026, 19:00 UTC

    📢 Fortinet corrige une SQLi critique dans FortiClientEMS (CVE-2026-21643) 📝 Selon un avis PSIRT de Fortinet publié le 6 février 2026, une vulnérabilité critique d’injection SQL affecte FortiClientEMS. 📖 cyberveille : https:// cyberveille.ch/posts/2026-02-1

    Earliest third-party post we hold.

    Source
    Mastodon post social
    Recorded time
    Precision
    To the minute
    Origin
    Claimed. The date the source gives.
    Quote check
    Not checked yet
    Snapshot
    No archived snapshot
    Used in metrics
    No, kept for the record
    Dispute this timestamp
    CISA KEV (CVE-2026-21643)ClaimedQuote verified13 Apr 2026

    Fortinet FortiClient EMS SQL Injection Vulnerability

    Added to CISA's KEV catalog on 2026-04-13.

    Recorded time
    Precision
    Date only (no time of day is shown)
    Origin
    Claimed. The date the source gives.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:ef8fffede5c47200…
    Used in metrics
    No, kept for the record
    Dispute this timestamp

  2. Vendor statement

    date onlysame dayUnverified: no archived copy, quote not checked yet

    Fortinet PSIRT FG-IR-25-1142CuratedQuote not checked yet

    2026-02-06: Initial publication

    Source
    Fortinet PSIRT FG-IR-25-1142 vendor advisory
    Recorded time
    Precision
    Date only (no time of day is shown)
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Not checked yet
    Snapshot
    No archived snapshot
    Used in metrics
    Yes
    Dispute this timestamp

  3. First workaround

    No official mitigation found yet.

  4. First fix

    date onlysame day

    Fortinet PSIRT FG-IR-25-1142 (Wayback snapshot 2026-02-07 08:40 UTC)CuratedQuote verified

    Upgrade to 7.4.5 or above

    Only 7.4.4 is affected; 7.4.5 was listed as the fix in the initial advisory (and likely shipped before it; not verified). Upper bound: fixed builds may have shipped earlier; only the date shown here is evidenced (R2).

    Recorded time
    Precision
    Date only (no time of day is shown)
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:3cc4eb6f45a926c6…
    Used in metrics
    Yes
    Dispute this timestamp

  5. Fixed for all versions

    date onlysame day

    Fortinet PSIRT FG-IR-25-1142 (Wayback snapshot 2026-02-07 08:40 UTC)CuratedQuote verified

    Upgrade to 7.4.5 or above

    Single affected branch (7.4); 8.0 and 7.2 are not affected.

    Recorded time
    Precision
    Date only (no time of day is shown)
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:3cc4eb6f45a926c6…
    Used in metrics
    Yes
    Dispute this timestamp

This advisory changed after publication

  1. FG-IR-25-1142

    Changed without a revision note

    SQLi in administrative interface

    Advisory now says the bug is exploited (earlier version: vendor not aware).

    • Exploitation status
    Exploitation status
    Beforevendor not aware of exploitation
    Aftervendor aware of exploitation
    Earlier version captured 30 Mar 2026, 13:37 UTC: archived copyLater version captured 8 Apr 2026, 03:53 UTC: archived copyRecovered from archived copiesSnapshots 7d47085556… and 5b98d3fa48…Incident page

Send this to your boss

No brief for this incident yet. We write one for every open incident and every critical bug exploited before a fix.

Affected products

  • FortiClient EMS
How we built this timeline

Coordinated/internal disclosure 6 Feb 2026 with the fix; exploitation came later (KEV 13 Apr 2026). The advisory changed after publication without a timeline entry: the sentence 'This has been observed to be exploited in the wild.' is absent from the 30 Mar 2026 Wayback snapshot and present in the 8 Apr 2026 one, with no timeline entry; the live page (22 Oct 2026) still shows 'Known Exploited No'.

Earlier captures label the CVSS temporal score (9.1) as 'CVSSv3 Score'; the current template shows the base score 9.8 with the same vector (a page redesign, not a re-score); 9.8 used. The only timeline entries are both 6 Feb 2026 (initial publication;

FortiEMS Cloud removed as not affected).

Related

Fortinet report card