ETK-2026-3565Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
HarnessRouter Docker images before 0.37.17 do not properly enforce session file boundaries. An attacker with an instance API key or authenticated console access can read files accessible to the service, potentially exposing stored secrets; in a specific Codex resume configuration, an agent may also cause writes outside its session. The read issue requires credentials associated with a session the caller can control.
mitigation
Upgrade the HarnessRouter Docker image to 0.37.17. If API keys or console access may have been exposed, rotate the secret key, console password, API keys, provider credentials, and other connected-service credentials, then restart the container.
fixed in 0.37.17
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.
- 2026-11-04 00:51Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-3565
{ "etk_id": "ETK-2026-3565", "cve_id": null, "display_id": "ETK-2026-3565", "ghsa_id": "GHSA-7vp4-rwx5-4j3f", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Authenticated arbitrary file access in HarnessRouter", "summary": "HarnessRouter Docker images before 0.37.17 do not properly enforce session file boundaries. An attacker with an instance API key or authenticated console access can read files accessible to the service, potentially exposing stored secrets; in a specific Codex resume configuration, an agent may also cause writes outside its session. The read issue requires credentials associated with a session the caller can control.", "mitigation": "Upgrade the HarnessRouter Docker image to 0.37.17. If API keys or console access may have been exposed, rotate the secret key, console password, API keys, provider credentials, and other connected-service credentials, then restart the container.", "vendor": "other", "product": "other:harnessrouter/harnessrouter (Docker image)", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 0.37.16" ], "ecosystem": "other", "fixed_versions": [ "0.37.17" ], "package_name": "harnessrouter/harnessrouter (Docker image)", "purl": null } ], "cwes": [ 22 ], "cvss_score": 9, "cvss_src": "ethiack_provisional", "cvss_vector": null, "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 16.612646483333332, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-11-04T00:51:36+00:00", "days": -1.074641086875, "is_lower_bound": true, "measured_at": "2026-11-05T02:39:05.301272+00:00", "url": "https://github.com/HarnessRouter/harnessrouter/security/advisories/GHSA-7vp4-rwx5-4j3f" } } }
published 2026-11-05 01:44Z
last change 2026-11-05 02:19Z
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.