CVE-2026-106174

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

GHSA-jq7m-wj67-4h5c ↗EUVD-2026-110616 ↗

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 FortiOS 8.0.0; >= 7.6.4, <= 7.6.6
ETK-2026-2745Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 32msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h30m
0
+2h
+6h
+8h
+10h
+12h

description

FortiOS 8.0.0 and versions 7.6.4 through 7.6.6 are affected by an improper locking flaw in the HTTPS management interface. An unauthenticated attacker that can reach the device over the network may make that management interface unavailable.

mitigation

Restrict HTTPS management access to trusted administrative networks and disable external exposure where possible. No fixed version is identified in the supplied evidence; apply a vendor-provided update when one is available.

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
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 06:54Z
Δ 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-10-27 06:54Z
    ghsa: trigger signal, started the run
  2. 2026-10-27 06:54Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2745",
  "cve_id": "CVE-2026-106174",
  "display_id": "CVE-2026-106174",
  "ghsa_id": "GHSA-jq7m-wj67-4h5c",
  "euvd_id": "EUVD-2026-110616",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper locking denial of service in FortiOS HTTPS management",
  "summary": "FortiOS 8.0.0 and versions 7.6.4 through 7.6.6 are affected by an improper locking flaw in the HTTPS management interface. An unauthenticated attacker that can reach the device over the network may make that management interface unavailable.",
  "mitigation": "Restrict HTTPS management access to trusted administrative networks and disable external exposure where possible. No fixed version is identified in the supplied evidence; apply a vendor-provided update when one is available.",
  "vendor": "Fortinet",
  "product": "FortiOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "8.0.0",
        ">= 7.6.4, <= 7.6.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FortiOS",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.526372633333333,
  "t0_at": "2026-10-27T06:54:54.066000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T06:54:54.066000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T06:54:54.066000+00:00",
      "url": "https://github.com/advisories/GHSA-jq7m-wj67-4h5c"
    }
  }
}

published 2026-10-27 10:12Z
last change 2026-10-27 13:52Z

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.