HarnessRouter
HarnessRouter: A workspace's API key could read and change sessions, files and responses of other workspaces in the same organization
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.4.2, < 0.31.7
Fixed in 0.31.7
Mitigation
Upgrade harnessrouter to 0.31.7 or later.
References
- Vendor advisory github.com/HarnessRouter/harnessrouter/securit…
- Patch github.com/HarnessRouter/harnessrouter/pull/41…
- Patch github.com/HarnessRouter/harnessrouter/commit/…
1 more
- Release notes github.com/HarnessRouter/harnessrouter/release…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.