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

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

GHSA-95fq-78jc-hrqp ↗

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.
rust tari_engine < 0.45.0
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1961Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/tari_engine
2d 18h 19msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −6.0dwaiting for further signals−2.8d
−6d
−4d
−2d
0

description

tari_engine fails to meter native work performed for certain WebAssembly engine operations. An attacker who can publish a template and submit a transaction can consume disproportionate CPU on validators, potentially disrupting consensus progress.

mitigation

No fixed release is recorded. Restrict untrusted template publication and transaction submission where possible, and apply an upstream release containing metering for this path when one is published.

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
37m
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-15 05:16Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1961",
  "cve_id": null,
  "display_id": "ETK-2026-1961",
  "ghsa_id": "GHSA-95fq-78jc-hrqp",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unmetered engine operations cause CPU exhaustion in tari_engine",
  "summary": "tari_engine fails to meter native work performed for certain WebAssembly engine operations. An attacker who can publish a template and submit a transaction can consume disproportionate CPU on validators, potentially disrupting consensus progress.",
  "mitigation": "No fixed release is recorded. Restrict untrusted template publication and transaction submission where possible, and apply an upstream release containing metering for this path when one is published.",
  "vendor": "rust",
  "product": "tari_engine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.45.0"
      ],
      "ecosystem": "rust",
      "fixed_versions": [],
      "package_name": "tari_engine",
      "purl": "pkg:cargo/tari_engine"
    }
  ],
  "cwes": [
    400
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.94288743333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T05:16:14+00:00",
      "days": -6.021918961909722,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:47.820632+00:00",
      "url": "https://github.com/tari-project/tari-ootle/security/advisories/GHSA-95fq-78jc-hrqp"
    }
  }
}

published 2026-10-18 10:51Z
last change 2026-10-21 05:31Z

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.