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

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

GHSA-9fr5-46w5-5f9r ↗

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.
pip:btclib <= 2026.10.3
fixed in 2026.10.4
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-551, no cve assigned
pkg:pypi/btclib
16d 18h 48msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −17dwaiting for further signals−17d
−15d
−10d
−5d
0

description

btclib versions before 2026.10.4 can consume excessive CPU while validating certain valid P2TR script-path transactions. An attacker can delay a service that validates transactions or blocks from untrusted sources, including peer-provided data.

mitigation

Upgrade btclib to version 2026.10.4 or later. Until upgrade, restrict untrusted transaction validation and apply resource limits where your deployment permits.

fixed in 2026.10.4

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.
–
agent run time
13m
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

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-03 22:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-551",
  "cve_id": null,
  "display_id": "ETK-2026-551",
  "ghsa_id": "GHSA-9fr5-46w5-5f9r",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Algorithmic denial of service in btclib tapscript validation",
  "summary": "btclib versions before 2026.10.4 can consume excessive CPU while validating certain valid P2TR script-path transactions. An attacker can delay a service that validates transactions or blocks from untrusted sources, including peer-provided data.",
  "mitigation": "Upgrade btclib to version 2026.10.4 or later. Until upgrade, restrict untrusted transaction validation and apply resource limits where your deployment permits.",
  "vendor": "pip",
  "product": "pip:btclib",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 2026.10.3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2026.10.4"
      ],
      "package_name": "btclib",
      "purl": "pkg:pypi/btclib"
    }
  ],
  "cwes": [
    407
  ],
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.015074816666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T22:17:01+00:00",
      "days": -17.312906443206018,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:36.138283+00:00",
      "url": "https://github.com/btclib-org/btclib/security/advisories/GHSA-9fr5-46w5-5f9r"
    }
  }
}

published 2026-10-04 10:46Z
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.