Quick answers
- Is CVE-2026-125330 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125330 being exploited in the wild.
- How severe is CVE-2026-125330?
- High severity, with a CVSS score of 7.5, published 10 November 2026.
- Which products and versions are affected?
- HarnessRouter 0.4.2 to 0.31.6.
- Is there a fix for CVE-2026-125330?
- Yes: fixed in 0.31.7. Until then: Upgrade to version 0.31.7 or later. Until upgrade is possible, restrict API key distribution and monitor cross-workspace access logs for unexpected activity. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125330 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-125330?
- Check whether you run HarnessRouter at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.31.7
Upgrade to version 0.31.7 or later. Until upgrade is possible, restrict API key distribution and monitor cross-workspace access logs for unexpected activity.
Technical details
The vulnerability is an authorization bypass in routes accepting session or response IDs. Routes validated only the organization membership but failed to check whether the API key held scope to the specific workspace being accessed. The flaw affected approximately 72 routes taking resource identifiers. Organization-wide keys and Default Workspace keys intentionally retain organization-wide access; only workspace-scoped keys (outside Default Workspace) were restricted, which the code did not enforce at the route level.
Affected products
- HarnessRouter HarnessRouter 0.4.2 to 0.31.6
Timeline
- 2026-11-10: disclosed
- 2026-10-06: patched: Fix merged to main branch prior to public disclosure