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

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

GHSA-c5j3-3rp9-c4rv ↗

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.
go:github.com/anacrolix/torrent >= 1.51.0, < 1.63
fixed in 1.63
CWE-248 Uncaught Exception
ETK-2026-4661Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/anacrolix/torrent
1d 10h 37msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+0h47m
0
+12h
+24h
+36h

description

Versions of github.com/anacrolix/torrent before 1.63 can be crashed by an unauthenticated remote peer through ut_holepunch rendezvous-message handling. The issue is reachable when an attacker can establish a peer connection; default settings that accept inbound peers expose affected clients.

mitigation

Upgrade github.com/anacrolix/torrent to version 1.63 or later. Until upgraded, restrict or disable inbound peer connections where operationally feasible.

fixed in 1.63

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
16m
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, 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-17 10:26Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4661",
  "cve_id": null,
  "display_id": "ETK-2026-4661",
  "ghsa_id": "GHSA-c5j3-3rp9-c4rv",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Remote denial of service in anacrolix/torrent ut_holepunch handling",
  "summary": "Versions of github.com/anacrolix/torrent before 1.63 can be crashed by an unauthenticated remote peer through ut_holepunch rendezvous-message handling. The issue is reachable when an attacker can establish a peer connection; default settings that accept inbound peers expose affected clients.",
  "mitigation": "Upgrade github.com/anacrolix/torrent to version 1.63 or later. Until upgraded, restrict or disable inbound peer connections where operationally feasible.",
  "vendor": "go",
  "product": "go:github.com/anacrolix/torrent",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.51.0, < 1.63"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "1.63"
      ],
      "package_name": "github.com/anacrolix/torrent",
      "purl": "pkg:golang/github.com/anacrolix/torrent"
    }
  ],
  "cwes": [
    248
  ],
  "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": 16.364521483333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T10:26:56+00:00",
      "days": -1.474862965613426,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T21:50:44.208952+00:00",
      "url": "https://github.com/anacrolix/torrent/security/advisories/GHSA-c5j3-3rp9-c4rv"
    }
  }
}

published 2026-11-17 11:02Z
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.