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

validatedZero produced an exploit or a check.

GHSA-jcgv-7262-j5p6 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−13h40mkevAttacks confirmed in the real world.
rust:postrust-proxy < 1.0.0
fixed in 1.0.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-3142Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/postrust-proxy
−3h29mTTV
15mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0hpublic poc+0hcheck available+10h11magent stopped
0
+3h
+6h
+9h
+12h
+15h

description

postrust-proxy versions before 1.0.0 can leave unauthenticated connections open until file descriptors are exhausted. Attackers able to reach a proxy listener may also bypass route restrictions where backends support protocol upgrades or normalize paths; backends that trust client-supplied forwarding headers may accept spoofed source addresses. Rate-limit behavior can also cause persistent client lockouts or weaken limits across routes.

mitigation

Upgrade postrust-proxy to version 1.0.0. Until upgraded, restrict listener access to trusted networks and ensure backends do not trust client-provided forwarding headers or rely solely on proxy route restrictions.

fixed in 1.0.0

check
available
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
15m
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).
−13h40m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, 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-30 19:03Z
  2. 2026-10-30 19:03Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3142",
  "cve_id": null,
  "display_id": "ETK-2026-3142",
  "ghsa_id": "GHSA-jcgv-7262-j5p6",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Connection exhaustion and route-policy bypasses in postrust-proxy",
  "summary": "postrust-proxy versions before 1.0.0 can leave unauthenticated connections open until file descriptors are exhausted. Attackers able to reach a proxy listener may also bypass route restrictions where backends support protocol upgrades or normalize paths; backends that trust client-supplied forwarding headers may accept spoofed source addresses. Rate-limit behavior can also cause persistent client lockouts or weaken limits across routes.",
  "mitigation": "Upgrade postrust-proxy to version 1.0.0. Until upgraded, restrict listener access to trusted networks and ensure backends do not trust client-provided forwarding headers or rely solely on proxy route restrictions.",
  "vendor": "rust",
  "product": "rust:postrust-proxy",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.0.0"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "1.0.0"
      ],
      "package_name": "postrust-proxy",
      "purl": "pkg:cargo/postrust-proxy"
    }
  ],
  "cwes": [
    22
  ],
  "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": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 15.242233516666667,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-31T05:14:41.954976+00:00",
      "days": -0.14487856400462962,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T08:43:19.770220+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-30T19:03:43+00:00",
      "days": -0.569172024375,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T08:43:19.770220+00:00",
      "url": "https://github.com/postrust/postrust/security/advisories/GHSA-jcgv-7262-j5p6"
    },
    "trigger_signal": {
      "at": "2026-10-30T19:03:43+00:00",
      "days": -0.569172024375,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T08:43:19.770220+00:00",
      "url": "https://github.com/postrust/postrust/security/advisories/GHSA-jcgv-7262-j5p6"
    }
  }
}

published 2026-10-31 04:59Z
last change 2026-10-31 08:37Z

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.