CVE-2026-95778

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

GHSA-9wpc-69v4-f98g ↗EUVD-2026-120063 ↗

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) HPE Morpheus Software >= 9.0, < 9.0.2
fixed in 9.0.2
ETK-2026-3965Zero's internal tracking ID, independent of the CVE number., permanent identifier
13h 24msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+27h21m
0
+2h
+4h
+6h
+8h
+10h

description

HPE Morpheus Software has a code-execution flaw corrected in version 9.0.2. An attacker with low-level access may be able to run code through the affected software; the available advisory material does not specify further preconditions or the affected version range.

mitigation

Upgrade HPE Morpheus Software to version 9.0.2. Until upgraded, restrict low-privilege access to the product and review accounts that can access it.

fixed in 9.0.2

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 14:00Z
Δ 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-09 14:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3965",
  "cve_id": "CVE-2026-95778",
  "display_id": "CVE-2026-95778",
  "ghsa_id": "GHSA-9wpc-69v4-f98g",
  "euvd_id": "EUVD-2026-120063",
  "status": "published",
  "anchor_state": "anchored",
  "title": "HPE Morpheus Software code execution flaw",
  "summary": "HPE Morpheus Software has a code-execution flaw corrected in version 9.0.2. An attacker with low-level access may be able to run code through the affected software; the available advisory material does not specify further preconditions or the affected version range.",
  "mitigation": "Upgrade HPE Morpheus Software to version 9.0.2. Until upgraded, restrict low-privilege access to the product and review accounts that can access it.",
  "vendor": "Hewlett Packard Enterprise (HPE)",
  "product": "HPE Morpheus Software",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.0, < 9.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.0.2"
      ],
      "package_name": "HPE Morpheus Software",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.8738326,
  "t0_at": "2026-11-09T14:00:34.169000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T14:00:34.169000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T14:00:34.169000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-95778"
    }
  }
}

published 2026-11-09 14:25Z
last change 2026-11-11 06:19Z

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.