CVE-2026-126147

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2026-123831 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Fortinet FortiMail >= 8.0.0, <= 8.0.1; >= 7.6.0, <= 7.6.6; >= 7.4.0, <= 7.4.8; >= 7.2.0, <= 7.2.9
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-4223Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 33msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Fortinet FortiMail 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, and all 7.2 releases are affected. An unauthenticated attacker may use crafted requests to run unauthorized code or commands.

mitigation

Restrict access to FortiMail management and exposed web interfaces to trusted networks until a vendor update or guidance is available. Monitor Fortinet advisories for a fixed release.

check
no
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.
–
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 21:29Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-11 21:29Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4223",
  "cve_id": "CVE-2026-126147",
  "display_id": "CVE-2026-126147",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-123831",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Fortinet FortiMail",
  "summary": "Fortinet FortiMail 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, and all 7.2 releases are affected. An unauthenticated attacker may use crafted requests to run unauthorized code or commands.",
  "mitigation": "Restrict access to FortiMail management and exposed web interfaces to trusted networks until a vendor update or guidance is available. Monitor Fortinet advisories for a fixed release.",
  "vendor": "Fortinet",
  "product": "FortiMail",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.0.0, <= 8.0.1",
        ">= 7.6.0, <= 7.6.6",
        ">= 7.4.0, <= 7.4.8",
        ">= 7.2.0, <= 7.2.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:U/RL:O/RC:R",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.401505,
  "t0_at": "2026-11-11T21:29:16.713000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T21:29:16.713000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T21:29:16.713000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126147"
    }
  }
}

published 2026-11-11 22:10Z
last change 2026-11-12 00:37Z

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.