CVE-2026-107656

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

GHSA-g63q-h893-6372 ↗EUVD-2026-109831 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19h10mkevAttacks confirmed in the real world.
Fortinet FortiSandbox >= 5.0.0, <= 5.0.6; >= 4.4.0, <= 4.4.9; >= 4.2.1, <= 4.2.8
CWE-288 Authentication Bypass Using an Alternate Path or Channel
ETK-2026-2651Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 17msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
public poc−19h10mtrigger signal (cve.org) +0hwaiting for further signals+2h
−18h
−12h
−6h
0

description

FortiSandbox 4.2, FortiSandbox 4.4 before 4.4.10, and FortiSandbox 5.0 before 5.0.7 are affected, along with the listed FortiSandbox PaaS 4.2, 4.4, and 5.0 releases. A remote attacker who can reach the HTTP interface may bypass authentication and run unauthorized commands or code.

mitigation

Upgrade FortiSandbox 4.4 to 4.4.10 or later and FortiSandbox 5.0 to 5.0.7 or later; move 4.2 deployments to a supported patched release. Restrict GUI and HTTP access to trusted administrative networks or a VPN while obtaining an applicable patched FortiSandbox PaaS 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
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 13:45Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−19h10m
Δ 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-10-26 13:45Z
    cve_org: trigger signal, started the run
  2. 2026-10-26 14:24Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2651",
  "cve_id": "CVE-2026-107656",
  "display_id": "CVE-2026-107656",
  "ghsa_id": "GHSA-g63q-h893-6372",
  "euvd_id": "EUVD-2026-109831",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in FortiSandbox HTTP interface",
  "summary": "FortiSandbox 4.2, FortiSandbox 4.4 before 4.4.10, and FortiSandbox 5.0 before 5.0.7 are affected, along with the listed FortiSandbox PaaS 4.2, 4.4, and 5.0 releases. A remote attacker who can reach the HTTP interface may bypass authentication and run unauthorized commands or code.",
  "mitigation": "Upgrade FortiSandbox 4.4 to 4.4.10 or later and FortiSandbox 5.0 to 5.0.7 or later; move 4.2 deployments to a supported patched release. Restrict GUI and HTTP access to trusted administrative networks or a VPN while obtaining an applicable patched FortiSandbox PaaS release.",
  "vendor": "Fortinet",
  "product": "FortiSandbox",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, <= 5.0.6",
        ">= 4.4.0, <= 4.4.9",
        ">= 4.2.1, <= 4.2.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FortiSandbox",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, <= 5.0.6",
        ">= 4.4.0, <= 4.4.9",
        ">= 4.2.1, <= 4.2.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FortiSandbox PaaS",
      "purl": null
    }
  ],
  "cwes": [
    288
  ],
  "cvss_score": 9.6,
  "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:F/RL:O/RC:C",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.4952309,
  "t0_at": "2026-10-26T13:45:03.962000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-25T18:34:43+00:00",
      "days": -0.7988537268518519,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T13:45:03.962000+00:00",
      "url": "https://github.com/Ghost-Bx1/Fortinet-Exploits-CVE-2026-39808-106173-107656"
    },
    "trigger_signal": {
      "at": "2026-10-26T13:45:03.962000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T13:45:03.962000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107656"
    }
  }
}

published 2026-10-26 14:12Z
last change 2026-10-26 17:59Z

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.