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

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

GHSA-38xx-4h6j-jmr3 ↗

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:libp2p-messaging <= 0.43.0
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-741, no cve assigned
pkg:cargo/libp2p-messaging
14d 20h 21msince last run
45mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+1.1d
0
+5d
+10d
+15d

description

libp2p-messaging can retain inbound stream tasks without enforcing its configured receive timeout, allowing connections to remain active beyond expected cleanup. A peer that can establish a P2P connection may consume handler capacity and memory and disrupt messaging for its connection.

mitigation

Configure strict total, per-peer, and per-source connection limits, and restrict messaging access to trusted peers where feasible. Apply an upstream patch or release that enforces per-stream read and write timeouts when available; no fixed version is recorded.

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
45m
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-05 07:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-741",
  "cve_id": null,
  "display_id": "ETK-2026-741",
  "ghsa_id": "GHSA-38xx-4h6j-jmr3",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Inbound stream timeout denial of service in libp2p-messaging",
  "summary": "libp2p-messaging can retain inbound stream tasks without enforcing its configured receive timeout, allowing connections to remain active beyond expected cleanup. A peer that can establish a P2P connection may consume handler capacity and memory and disrupt messaging for its connection.",
  "mitigation": "Configure strict total, per-peer, and per-source connection limits, and restrict messaging access to trusted peers where feasible. Apply an upstream patch or release that enforces per-stream read and write timeouts when available; no fixed version is recorded.",
  "vendor": "rust",
  "product": "rust:libp2p-messaging",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.43.0"
      ],
      "ecosystem": "rust",
      "fixed_versions": [],
      "package_name": "libp2p-messaging",
      "purl": "pkg:cargo/libp2p-messaging"
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.20239433333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T07:18:17+00:00",
      "days": -15.897958248368056,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:20.614454+00:00",
      "url": "https://github.com/tari-project/tari-ootle/security/advisories/GHSA-38xx-4h6j-jmr3"
    }
  }
}

published 2026-10-06 07:45Z
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.