CVE-2026-95745

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

GHSA-2hqr-gfpj-5pcg ↗EUVD-2026-116162 ↗

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.
Hewlett Packard Enterprise (HPE) Fabric Composer >= 7.4.0, <= 7.4.0; >= 7.0.0, <= 7.3.4
ETK-2026-3405Zero's internal tracking ID, independent of the CVE number., permanent identifier
23h 42msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h27m
0
+2h
+6h
+8h
+10h
+12h

description

Fabric Composer is affected by an API flaw that can disrupt management services. A remote attacker can cause the services to become unavailable without authenticating if they can reach the affected API.

mitigation

Restrict access to the Fabric Composer API to trusted administrative networks and hosts until vendor remediation is available. Monitor management-service availability and apply vendor updates when provided.

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-11-03 19:51Z
Δ 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-03 19:51Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3405",
  "cve_id": "CVE-2026-95745",
  "display_id": "CVE-2026-95745",
  "ghsa_id": "GHSA-2hqr-gfpj-5pcg",
  "euvd_id": "EUVD-2026-116162",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated API denial of service in Fabric Composer",
  "summary": "Fabric Composer is affected by an API flaw that can disrupt management services. A remote attacker can cause the services to become unavailable without authenticating if they can reach the affected API.",
  "mitigation": "Restrict access to the Fabric Composer API to trusted administrative networks and hosts until vendor remediation is available. Monitor management-service availability and apply vendor updates when provided.",
  "vendor": "Hewlett Packard Enterprise (HPE)",
  "product": "Fabric Composer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.4.0, <= 7.4.0",
        ">= 7.0.0, <= 7.3.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Fabric Composer",
      "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": 14.822522233333334,
  "t0_at": "2026-11-03T19:51:01.966000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T19:51:01.966000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T19:51:01.966000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-95745"
    }
  }
}

published 2026-11-03 20:28Z
last change 2026-11-04 18:01Z

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.