← back to feed
ETK-2026-3614Zero's internal tracking ID, independent of the CVE number.

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

validatedZero produced an exploit or a check.

GHSA-gf7m-w8pf-6f68 ↗

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).kevAttacks confirmed in the real world.
other:harnessrouter/harnessrouter (Docker image) < 0.37.17
fixed in 0.37.17
ETK-2026-3614Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.0ethiack provisional
−11h58mTTV
22mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org, not yet published
trigger signal −1.8dcheck available−0.5dagent stopped
−1d
0

description

Harnessrouter Docker image deployments not updated to 0.37.17 can fail to enforce workspace and organization isolation on plug, attachment, and environment operations. An authenticated attacker may access or alter resources belonging to another workspace, and some shared-instance cases can expose attachment metadata or overwrite plug records across organizations. Exploitation requires access through an authenticated route, with the available impact depending on the credential scope and deployment configuration.

mitigation

Upgrade the harnessrouter Docker image to version 0.37.17. Until upgraded, restrict access to affected authenticated interfaces and limit workspace-scoped credentials to trusted users and services.

fixed in 0.37.17

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 02:32Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3614",
  "cve_id": null,
  "display_id": "ETK-2026-3614",
  "ghsa_id": "GHSA-gf7m-w8pf-6f68",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-tenant authorization flaw in harnessrouter",
  "summary": "Harnessrouter Docker image deployments not updated to 0.37.17 can fail to enforce workspace and organization isolation on plug, attachment, and environment operations. An authenticated attacker may access or alter resources belonging to another workspace, and some shared-instance cases can expose attachment metadata or overwrite plug records across organizations. Exploitation requires access through an authenticated route, with the available impact depending on the credential scope and deployment configuration.",
  "mitigation": "Upgrade the harnessrouter Docker image to version 0.37.17. Until upgraded, restrict access to affected authenticated interfaces and limit workspace-scoped credentials to trusted users and services.",
  "vendor": "other",
  "product": "other:harnessrouter/harnessrouter (Docker image)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.37.17"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "0.37.17"
      ],
      "package_name": "harnessrouter/harnessrouter (Docker image)",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 21.723750683333332,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-11-05T10:53:18.667416+00:00",
      "days": -0.49843376116898147,
      "is_lower_bound": true,
      "measured_at": "2026-11-05T22:51:03.492371+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-04T02:32:43+00:00",
      "days": -1.8460688007060184,
      "is_lower_bound": true,
      "measured_at": "2026-11-05T22:51:03.492371+00:00",
      "url": "https://github.com/HarnessRouter/harnessrouter/security/advisories/GHSA-gf7m-w8pf-6f68"
    }
  }
}

published 2026-11-05 10:31Z
last change 2026-11-05 22:47Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.