CVE-2026-123864

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

GHSA-m526-rv55-w6mr ↗EUVD-2026-123683 ↗

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.
nodejs node < 22.23.5; >= 23.0.0, < 24.22.3; >= 25.0.0, < 26.13.1
fixed in 22.23.5, 24.22.3, 26.13.1
ETK-2026-4676Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 07h 14msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+140h34m
0
+2h
+4h
+6h
+8h
+10h

description

Node.js HTTPS servers in the affected 22.x, 24.x, and 26.x lines can expose memory from other connections because of unsafe re-entrant request processing. An unauthenticated remote client may recover sensitive request or TLS data when application handlers send response headers before the request body is complete and handle request-body data.

mitigation

Upgrade Node.js 24.x to 24.22.3 or later, or Node.js 26.x to 26.13.1 or later. For 22.x, move to a supported fixed release; until then, revise HTTPS handlers to avoid sending response headers before request bodies finish.

fixed in 22.23.5, 24.22.3, 26.13.1

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.37%30th percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 18:17Z
Δ 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-11 18:17Z
  2. 2026-11-11 18:17Z
  3. 2026-11-17 13:26Z
    Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' Data

this entry in the feed

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

{
  "etk_id": "ETK-2026-4676",
  "cve_id": "CVE-2026-123864",
  "display_id": "CVE-2026-123864",
  "ghsa_id": "GHSA-m526-rv55-w6mr",
  "euvd_id": "EUVD-2026-123683",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free memory disclosure in Node.js HTTPS",
  "summary": "Node.js HTTPS servers in the affected 22.x, 24.x, and 26.x lines can expose memory from other connections because of unsafe re-entrant request processing. An unauthenticated remote client may recover sensitive request or TLS data when application handlers send response headers before the request body is complete and handle request-body data.",
  "mitigation": "Upgrade Node.js 24.x to 24.22.3 or later, or Node.js 26.x to 26.13.1 or later. For 22.x, move to a supported fixed release; until then, revise HTTPS handlers to avoid sending response headers before request bodies finish.",
  "vendor": "nodejs",
  "product": "node",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.0.0, < 22.23.5",
        ">= 23.0.0, < 24.22.3",
        ">= 25.0.0, < 26.13.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "22.23.5",
        "24.22.3",
        "26.13.1"
      ],
      "package_name": "node",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H",
  "epss_score": 0.0037,
  "epss_percentile": 0.3085,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.182091233333335,
  "t0_at": "2026-11-11T18:17:56.773000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T18:17:56.773000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T18:17:56.773000+00:00",
      "url": "https://thehackernews.com/2026/11/nodejs-fixes-16-flaws-including-http2.html"
    }
  }
}

published 2026-11-17 14:34Z
last change 2026-11-18 21:43Z

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.