# CVE-2026-6823: HKUDS OpenHarness Insecure Default Remote Channel Allowlist

> Attackers can bypass access controls and read files via insecure default allowlists in HKUDS OpenHarness remote channels.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-564h-hx6x-wg47

## What is CVE-2026-6823?

CVE-2026-6823 is a high-severity vulnerability in HKUDS OpenHarness, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HKUDS OpenHarness prior to PR #147 remediation contains an insecure default configuration vulnerability where remote channels inherit allow_from = ["*"] permitting arbitrary remote senders to pass admission checks. Attackers who can reach the configured channel can bypass access controls and reach host-backed agent runtimes, potentially leading to unauthorized file disclosure and read access through default-enabled read-only tools.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Hkuds Openharness.

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

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

## Is CVE-2026-6823 being exploited?

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

## Other vulnerabilities in HKUDS OpenHarness

- [CVE-2026-7551](https://insights.sbomify.com/CVE-2026-7551/): HKUDS OpenHarness Remote Command Execution via /bridge Slash Command (high 8.7)
- [CVE-2026-6819](https://insights.sbomify.com/CVE-2026-6819/): HKUDS OpenHarness Plugin Management Command Exposure (high 8.7)
- [CVE-2026-40515](https://insights.sbomify.com/CVE-2026-40515/): OpenHarness Permission Bypass via grep and glob root argument (high 8.7)
- [CVE-2026-40502](https://insights.sbomify.com/CVE-2026-40502/): OpenHarness Remote Administrative Command Injection via Gateway Handler (high 8.7)
- [CVE-2026-40516](https://insights.sbomify.com/CVE-2026-40516/): OpenHarness SSRF via web_fetch and web_search (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6823 is a high-severity vulnerability in HKUDS OpenHarness, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6823 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-6823/ (Markdown: https://insights.sbomify.com/CVE-2026-6823/index.md)
```

## Sources

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

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