CVE-2026-73793

validatingZero is analyzing and reversing it now.

GHSA-gg8w-382j-74wv ↗EUVD-2026-100948 ↗

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 NonStop Middleware T1155L01^AAF and earlier
CWE-502 Deserialization of Untrusted Data
ETK-2026-1839Zero's internal tracking ID, independent of the CVE number., permanent identifier
54mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0dvalidating
0
+2d
+4d
+6d
+8d

description

HPE NonStop Middleware is affected by insecure deserialization and secret-key handling weaknesses. An attacker with high privileges and network access may be able to affect the confidentiality, integrity, or availability of an affected deployment.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict network access to the middleware and limit privileged accounts to trusted administrators. Apply HPE-provided updates when they become available; no fixed version is recorded in the advisory.

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.36%28th percentile
agent run time
54m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 09:38Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-14 09:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1839",
  "cve_id": "CVE-2026-73793",
  "display_id": "CVE-2026-73793",
  "ghsa_id": "GHSA-gg8w-382j-74wv",
  "euvd_id": "EUVD-2026-100948",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Deserialization flaw in HPE NonStop Middleware",
  "summary": "HPE NonStop Middleware is affected by insecure deserialization and secret-key handling weaknesses. An attacker with high privileges and network access may be able to affect the confidentiality, integrity, or availability of an affected deployment.",
  "mitigation": "Restrict network access to the middleware and limit privileged accounts to trusted administrators. Apply HPE-provided updates when they become available; no fixed version is recorded in the advisory.",
  "vendor": "Hewlett Packard Enterprise",
  "product": "HPE NonStop Middleware",
  "affected": [
    {
      "affected_notes": [
        "T1155L01^AAF and earlier"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "HPE NonStop Middleware",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 7.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:H",
  "epss_score": 0.0036,
  "epss_percentile": 0.2821,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.174915516666667,
  "t0_at": "2026-10-14T09:38:03.947000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T09:38:03.947000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T09:38:03.947000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-73793"
    }
  }
}

published 2026-10-17 03:35Z
last change 2026-10-22 10:54Z

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.