DaystoPatch

FortinetExploited incident

FortiSandbox second-order OS command injection via the start-VNC feature

CVE-2026-25089Critical, CVSS 9.8In CISA's Known Exploited Vulnerabilities catalog since 16 Jul 2026

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

Response

Silence
0h
First public report to first vendor statement
Exposure
same day
First public report to first fix
Follow-through
same day
First public report to a fix for every supported version
  • 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

    CVE record CVE-2026-25089 (CNA: Fortinet)CuratedQuote verified

    "datePublished":"2026-06-09T14:27:47.492Z"

    Internally discovered; Fortinet's advisory is the first public signal. Exploitation of this and two other FortiSandbox CVEs was reported by Defused on 2026-06-15 (Help Net Security, 2026-06-16).

    Recorded time
    Precision
    To the minute
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:332853d0588b46ef…
    Used in metrics
    Yes
    Dispute this timestamp
    6 more sources for this moment
    Fortinet advisory FG-IR-26-141ClaimedQuote verified9 Jun 2026

    Second-Order OS Command Injection via JSON Input on start vnc feature

    The vendor's own disclosure.

    Source
    Fortinet advisory FG-IR-26-141 vendor advisory
    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:63aeeb7d99399ae4…
    Used in metrics
    No, kept for the record
    Dispute this timestamp
    CVE.org record CVE-2026-25089ClaimedQuote verified9 Jun 2026, 14:27 UTC

    A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8,

    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:332853d0588b46ef…
    Used in metrics
    No, kept for the record
    Dispute this timestamp
    Bluesky postClaimedQuote not checked yet9 Jun 2026, 15:17 UTC

    The flaw, tracked as CVE-2026-25089 and assigned a CVSSv3 score of 9.1 (Critical), affects multiple versions of FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS deployments.

    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 yet16 Jun 2026, 09:39 UTC

    Fortinet Flaws Exposed to Active Exploitation Critical vulnerabilities in Fortinet's FortiSandbox platform are under active attack, with multiple flaws, including CVE-2026-39813, CVE-2026-39808, and

    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-25089)ClaimedQuote verified16 Jul 2026

    Fortinet FortiSandbox OS Command Injection Vulnerability

    Added to CISA's KEV catalog on 2026-07-16.

    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
    Hacker NewsClaimedQuote not checked yet16 Jul 2026, 22:07 UTC

    CVE-2026-25089: FortiSandbox unauthenticated command injection added to CISA KEV

    Earliest third-party post we hold. An independent author on another platform posted within 48 hours. Used for unreviewed incidents only, never graded.

    Source
    Hacker News hn
    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

  2. Vendor statement

    at disclosure

    CVE record CVE-2026-25089 (CNA: Fortinet)CuratedQuote verified

    "datePublished":"2026-06-09T14:27:47.492Z"

    Recorded time
    Precision
    To the minute
    Origin
    Curated. Found by a researcher, with a verbatim quote and link.
    Quote check
    Found in the archived copy
    Snapshot
    sha256:332853d0588b46ef…
    Used in metrics
    Yes
    Dispute this timestamp
    1 more source for this moment
    Fortinet PSIRT FG-IR-26-141CuratedQuote verified9 Jun 2026

    2026-06-09: Initial publication

    Source
    Fortinet PSIRT FG-IR-26-141 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
    Found in the archived copy
    Snapshot
    sha256:fdeaa49647bf3f55…
    Used in metrics
    No, kept for the record
    Dispute this timestamp

  3. First workaround

    No official mitigation found yet.

  4. First fix

    date onlysame day

    Fortinet PSIRT FG-IR-26-112 (Wayback snapshot 2026-04-14 18:44 UTC; same fixed builds)CuratedQuote verified

    Upgrade to 5.0.6 or above

    R2: FortiSandbox 5.0.6 and 4.4.9, the fixes FG-IR-26-141 names for this CVE, were already listed as available fixes in FG-IR-26-112 on 2026-04-14, eight weeks before this advisory. Upper bound: they may have shipped earlier.

    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:f8db66255e630da1…
    Used in metrics
    Yes
    Dispute this timestamp
    1 more source for this moment
    Fortinet PSIRT FG-IR-26-141 (Wayback snapshot 2026-06-10 05:43 UTC)CuratedQuote verified9 Jun 2026

    Upgrade to 5.0.6 or above

    Fixed versions as listed at this advisory's publication.

    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:42cf141b20540723…
    Used in metrics
    No, kept for the record
    Dispute this timestamp

  5. Fixed for all versions

    date onlysame day

    Fortinet PSIRT FG-IR-26-112 (Wayback snapshot 2026-04-14 18:44 UTC)CuratedQuote verified

    Upgrade to 4.4.9 or above

    R2/R6: both on-premises lines (5.0 → 5.0.6, 4.4 → 4.4.9) had their fixed builds by 2026-04-14 (upper bound); FortiSandbox Cloud/PaaS 5.0 also move to 5.0.6.

    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:f8db66255e630da1…
    Used in metrics
    Yes
    Dispute this timestamp

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

  • FortiSandbox
  • FortiSandbox Cloud
  • FortiSandbox PaaS
How we built this timeline

Split out of fortinet-cve-2026-39808 on 23 Oct 2026 under rule R7: Defused reported one campaign exploiting CVE-2026-39813, CVE-2026-39808 and CVE-2026-25089 together ('Attackers have been spotted exploiting three vulnerabilities (CVE-2026-39813, CVE-2026-39808, CVE-2026-25089) in FortiSandbox', Help Net Security 16 Jun 2026), but CVE-2026-25089 was disclosed on 9 Jun 2026, 56 days after the other two (14 Apr 2026), so it is its own incident. Cross-reference: fortinet-cve-2026-39808.

Coordinated/internal disclosure; the fixed builds predate both the advisory and exploitation, so exploited before a fix is false (R4). Defused said one public exploit for this CVE was 'vibecoded, and likely faulty'.

CVSS: advisory 9.8 (CNA record 9.1). KEV 16 Jul 2026.

The advisory still says 'Known Exploited No'.

Related

Fortinet report card