CVE-2026-79829

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

GHSA-vq9w-x8hf-mm54 ↗EUVD-2026-101999 ↗

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 HTTP WEBSERVER T1144L24^AAL and earlier
CWE-20 Improper Input Validation
ETK-2026-1675Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 14h 39msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+44h09m
0
+2h
+4h
+6h
+8h
+10h

description

HPE NonStop HTTP WEBSERVER is affected by a memory-corruption flaw that can disrupt service and potentially halt the system. An unauthenticated remote attacker may trigger the condition when they can reach the HTTP service.

mitigation

Restrict network access to the HTTP service to trusted clients and networks until remediation is applied. Contact HPE for affected-version confirmation and vendor-provided update or workaround guidance.

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.
0.40%32nd percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 10:03Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1675",
  "cve_id": "CVE-2026-79829",
  "display_id": "CVE-2026-79829",
  "ghsa_id": "GHSA-vq9w-x8hf-mm54",
  "euvd_id": "EUVD-2026-101999",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory corruption in HPE NonStop HTTP WEBSERVER",
  "summary": "HPE NonStop HTTP WEBSERVER is affected by a memory-corruption flaw that can disrupt service and potentially halt the system. An unauthenticated remote attacker may trigger the condition when they can reach the HTTP service.",
  "mitigation": "Restrict network access to the HTTP service to trusted clients and networks until remediation is applied. Contact HPE for affected-version confirmation and vendor-provided update or workaround guidance.",
  "vendor": "Hewlett Packard Enterprise",
  "product": "HPE NonStop HTTP WEBSERVER",
  "affected": [
    {
      "affected_notes": [
        "T1144L24^AAL and earlier"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "HPE NonStop HTTP WEBSERVER",
      "purl": null
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
  "epss_score": 0.004,
  "epss_percentile": 0.3295,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.70511395,
  "t0_at": "2026-10-15T10:03:58.372000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T10:03:58.372000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T10:03:58.372000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-79829"
    }
  }
}

published 2026-10-15 12:31Z
last change 2026-10-21 19:22Z

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.