ETK-2026-312Zero's internal tracking ID, independent of the CVE number.

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

GHSA-x5rw-q4pp-hg5g ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:devalue >= 5.8.0, <= 5.9.2
fixed in 5.9.3
ETK-2026-312, no cve assigned
pkg:npm/devalue
18d 23h 00msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −20dwaiting for further signals−19d
−15d
−10d
−5d
0

description

devalue versions before 5.9.3 can leave an internal promise rejection unhandled when stringifyAsync serializes multiple promises. This may terminate a Node.js process when a later promise rejects before an earlier promise settles, particularly where request-influenced asynchronous timing or failures are possible.

mitigation

Upgrade devalue to version 5.9.3 or later. Until upgraded, avoid passing multiple request-influenced promises to stringifyAsync where their rejection timing may vary.

fixed in 5.9.3

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.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-01 15:15Z
    ghsa: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/ETK-2026-312

{
  "etk_id": "ETK-2026-312",
  "cve_id": null,
  "display_id": "ETK-2026-312",
  "ghsa_id": "GHSA-x5rw-q4pp-hg5g",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unhandled promise rejection in devalue async serialization",
  "summary": "devalue versions before 5.9.3 can leave an internal promise rejection unhandled when `stringifyAsync` serializes multiple promises. This may terminate a Node.js process when a later promise rejects before an earlier promise settles, particularly where request-influenced asynchronous timing or failures are possible.",
  "mitigation": "Upgrade devalue to version 5.9.3 or later. Until upgraded, avoid passing multiple request-influenced promises to `stringifyAsync` where their rejection timing may vary.",
  "vendor": "npm",
  "product": "npm:devalue",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.8.0, <= 5.9.2"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "5.9.3"
      ],
      "package_name": "devalue",
      "purl": "pkg:npm/devalue"
    }
  ],
  "cwes": null,
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.576491083333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T15:15:13+00:00",
      "days": -19.566418022916668,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:50:51.540001+00:00",
      "url": "https://github.com/advisories/GHSA-x5rw-q4pp-hg5g"
    }
  }
}

published 2026-10-02 06:38Z
last change 2026-10-21 04:45Z

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.