CVE-2026-76659

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

GHSA-p85w-h249-v9x9 ↗EUVD-2026-101809 ↗

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 TCP/IP UTILITIES T8602L01^BAA and earlier
CWE-306 Missing Authentication for Critical Function
ETK-2026-1875Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 23h 55msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+109h14m
0
+2h
+4h
+6h
+8h
+10h

description

HPE NonStop TCP/IP UTILITIES includes a vulnerability in its finger daemon. An unauthenticated remote attacker may be able to disrupt service if they can reach the finger service over the network.

mitigation

Restrict network access to the finger daemon to trusted hosts, or disable the service where it is not required. Obtain and apply vendor-provided updates when HPE publishes a fixed 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.
–
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.
0.31%21st percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 01:31Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-15 01:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1875",
  "cve_id": "CVE-2026-76659",
  "display_id": "CVE-2026-76659",
  "ghsa_id": "GHSA-p85w-h249-v9x9",
  "euvd_id": "EUVD-2026-101809",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated denial of service in NonStop finger daemon",
  "summary": "HPE NonStop TCP/IP UTILITIES includes a vulnerability in its finger daemon. An unauthenticated remote attacker may be able to disrupt service if they can reach the finger service over the network.",
  "mitigation": "Restrict network access to the finger daemon to trusted hosts, or disable the service where it is not required. Obtain and apply vendor-provided updates when HPE publishes a fixed release.",
  "vendor": "Hewlett Packard Enterprise",
  "product": "HPE NonStop TCP/IP UTILITIES",
  "affected": [
    {
      "affected_notes": [
        "T8602L01^BAA and earlier"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "HPE NonStop TCP/IP UTILITIES",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "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": 0.0031,
  "epss_percentile": 0.2193,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.144643033333333,
  "t0_at": "2026-10-15T01:31:59.344000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T01:31:59.344000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T01:31:59.344000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76659"
    }
  }
}

published 2026-10-17 12:32Z
last change 2026-10-21 13:29Z

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.