# CVE-2026-114361: HarnessRouter Identity Mode app.py improper authorization


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-cjch-h263-r66v, GHSA-qrr8-m92f-7vfp

## What is CVE-2026-114361?

CVE-2026-114361 is a medium-severity vulnerability in HarnessRouter, published on 21 Oct 2026. 

### Official description

A vulnerability was detected in HarnessRouter up to 0.31.10. This affects an unknown function of the file gateway/app.py of the component Identity Mode. Performing a manipulation of the argument X-Harness-Org/X-Harness-Member results in improper authorization. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is reported as difficult. Upgrading to version 0.31.11 mitigates this issue. The patch is named 48a26cdf9c4544d2c88d1a07f0777f063f1d753f. The affected component should be upgraded.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-114361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114361 is a medium-severity vulnerability in HarnessRouter, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114361 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-114361/ (Markdown: https://insights.sbomify.com/CVE-2026-114361/index.md)
```

## Sources

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

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