# CVE-2026-125330: HarnessRouter is a self-hosted unified API for agent harnesses.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-9pjr-97x3-c4wv

## What is CVE-2026-125330?

CVE-2026-125330 is a high-severity vulnerability in harnessrouter, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-125330?


## How do I fix CVE-2026-125330?

No fix has been published for CVE-2026-125330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125330 being exploited?

There is no known exploitation of CVE-2026-125330 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125330 and fix it if it is affected.

What it is: CVE-2026-125330 is a high-severity vulnerability in harnessrouter, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125330 in the wild and no public exploit code.

Affected product: harnessrouter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125330/ (Markdown: https://insights.sbomify.com/CVE-2026-125330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125330
- OSV: https://osv.dev/vulnerability/CVE-2026-125330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125330/
Summaries are generated and may contain mistakes; the official description above is the record.