# CVE-2026-22682: OpenHarness Improper Access Control via File Tools

> Attackers can bypass file access controls in OpenHarness to read or modify sensitive local files by exploiting inconsistent permission checks in file tools.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-43rx-99w7-v5fh

## What is CVE-2026-22682?

CVE-2026-22682 is a high-severity missing authorization vulnerability in HKUDS OpenHarness, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenHarness prior to commit 166fcfe contains an improper access control vulnerability in built-in file tools due to inconsistent parameter handling in permission enforcement, allowing attackers who can influence agent tool execution to read arbitrary local files outside the intended repository scope. Attackers can exploit the path parameter not being passed to the PermissionChecker in read_file, write_file, edit_file, and notebook_edit tools to bypass deny rules and access sensitive files such as configuration files, credentials, and SSH material, or create and overwrite files in restricted host paths in full_auto mode.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-22682 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22682 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22682 is a high-severity missing authorization vulnerability in HKUDS OpenHarness, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22682 exists.

Affected product: HKUDS OpenHarness. 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-22682/ (Markdown: https://insights.sbomify.com/CVE-2026-22682/index.md)
```

## Sources

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

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