Workspace API keys can access other workspaces' data in HarnessRouter
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
HarnessRouter from 0.4.2 before 0.31.7 checks only the caller's organization on routes that accept a session ID or response ID, and does not enforce the workspace scope of non-default workspace API keys (CWE-639). A key holder who learns a non-guessable identifier from another workspace in the same organization can read sessions, files and responses, overwrite files, cancel or delete sessions, and publish share links. The issue does not cross organization boundaries, and console users, organization keys and Default Workspace keys keep organization-wide access by design.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
Description from the CNA
HarnessRouter is a self-hosted unified API for agent harnesses. From version 0.4.2 until 0.31.7, routes that accept a session ID or response ID validate only the caller's organization and do not enforce the workspace scope of a non-default workspace API key. A key holder who learns a non-guessable identifier from another workspace in the same organization can read sessions, conversation turns, files, traces, and responses, overwrite files, cancel or delete sessions, and publish share links. The issue does not cross organization boundaries, and console users, organization keys, and Default Workspace keys intentionally retain organization-wide access. This issue is fixed in version 0.31.7.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| HarnessRouter | harnessrouter | 0.4.2 to before 0.31.7 | 0.31.7 | Patch available | CNA |
- harnessrouter VendorHarnessRouter Affected 0.4.2 to before 0.31.7 Fixed in 0.31.7 Patch available CNA
Remediation
Upgrade HarnessRouter to version 0.31.7, which fixes this issue. The sources list no other fixed version for harnessrouter.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
- Fix · CNA harnessrouter (HarnessRouter) Fixed in 0.31.7
Timeline
- 2026-11-10 Threatist record created from CVE-2026-125330
- 2026-11-12 Priority changed: MEDIUM → LOW
- 2026-11-14 CISA SSVC decision points changed
References
Other 4
- https://github.com/HarnessRouter/harnessrouter/security/advisories/GHSA-9pjr-97x3-c4wv
- https://github.com/HarnessRouter/harnessrouter/pull/417
- https://github.com/HarnessRouter/harnessrouter/commit/249c6cc9ab51a24a78f4e9809d356718f2ef74b1
- https://github.com/HarnessRouter/harnessrouter/releases/tag/v0.31.7
More HarnessRouter vulnerabilities
- TI-2026-89066 Missing authorization in HarnessRouter allows connection rewrites CVSS 3.1CRITICAL 9.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences