CVE-2026-104286

validatedZero produced an exploit or a check.

GHSA-6gxc-3vv7-7w24 ↗EUVD-2026-91042 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+2h58mkevAttacks confirmed in the real world.+36m
Fortinet FortiMail 8.0.0; >= 7.6.0, <= 7.6.5; >= 7.4.0, <= 7.4.6; >= 7.2.0, <= 7.2.9; >= 7.0.0, <= 7.0.9
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-273, permanent identifier
+3h28mTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hkev+0h36mpublic poc+2h58mcheck available+3h28magent stopped
0
+1h
+2h

description

Fortinet FortiMail versions 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, and 7.2.0–7.2.9 are affected. An unauthenticated remote attacker may place files on the underlying system through the appliance's HTTP or HTTPS service; exposure requires network access to that service.

mitigation

Restrict HTTP and HTTPS access to trusted management networks and block unnecessary external access. No fixed release is identified in the supplied advisory; apply a vendor-provided update when available.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
2.2%82nd percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 19:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2h58m
Δ to kevAttacks confirmed in the real world.
+36m

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-01 00:00Z
  2. 2026-10-01 00:00Z
  3. 2026-10-01 00:00Z
  4. 2026-10-01 19:17Z
    cve_org: trigger signal, started the run
  5. 2026-10-02 01:44Z
  6. 2026-10-02 05:49Z
    Critical FortiMail Zero-Day Flaw Exploited in Attacks Allows Unauthenticated Arbitrary File Writes

this entry in the feed

GET /api/v1/feed/CVE-2026-104286

{
  "etk_id": "ETK-2026-273",
  "cve_id": "CVE-2026-104286",
  "display_id": "CVE-2026-104286",
  "ghsa_id": "GHSA-6gxc-3vv7-7w24",
  "euvd_id": "EUVD-2026-91042",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated path traversal in Fortinet FortiMail",
  "summary": "Fortinet FortiMail versions 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, and 7.2.0–7.2.9 are affected. An unauthenticated remote attacker may place files on the underlying system through the appliance's HTTP or HTTPS service; exposure requires network access to that service.",
  "mitigation": "Restrict HTTP and HTTPS access to trusted management networks and block unnecessary external access. No fixed release is identified in the supplied advisory; apply a vendor-provided update when available.",
  "vendor": "Fortinet",
  "product": "FortiMail",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "8.0.0",
        ">= 7.6.0, <= 7.6.5",
        ">= 7.4.0, <= 7.4.6",
        ">= 7.2.0, <= 7.2.9",
        ">= 7.0.0, <= 7.0.9"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FortiMail",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C",
  "epss_score": 0.022,
  "epss_percentile": 0.8227,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 11.475217366666667,
  "t0_at": "2026-10-01T19:17:38.938000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T22:45:16.506680+00:00",
      "days": 0.14418482268518518,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T19:17:38.938000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-01T19:54:04.930800+00:00",
      "days": 0.025300842592592594,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T19:17:38.938000+00:00",
      "precision": "exact",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-104286"
    },
    "public_poc": {
      "at": "2026-10-01T22:15:42+00:00",
      "days": 0.12364655092592593,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T19:17:38.938000+00:00",
      "url": "https://github.com/ShadowForge-Cyber/CVE-2026-104286-POC"
    },
    "trigger_signal": {
      "at": "2026-10-01T19:17:38.938000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T19:17:38.938000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104286"
    }
  }
}

published 2026-10-01 20:01Z
last change 2026-10-21 06:02Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.