Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach configured OpenHarness remote channel
-
DeliverySend message passing default allow_from ['*']
-
ExploitBypass admission as trusted sender
-
ExecutionReach host-backed agent runtime
-
PersistInvoke default read-only tools
-
ImpactDisclose host files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that at least one remote channel (Telegram, Slack, Discord, or Feishu) is enabled with the default or explicit allow_from = ["*"] allowlist - the insecure default before PR #147 - and that the attacker can reach that specific configured channel (CVSS AT:P). No credentials or approved identity on the gateway are needed once the channel is reachable (PR:N), and no user interaction is required. Limiting factors: exploitation is scoped to whatever the default-enabled read-only tools expose (file disclosure/read access, not write or code execution), and reachability of closed messaging channels may require the attacker to know or join the channel; operators who set specific allow_from IDs or leave it empty (deny-all) are not exposed. |
| Impact | Signals are mixed. The CVSS 4.0 base of 8.3 (High) reflects a network vector with low complexity and no privileges (AV:N/AC:L/PR:N) but an explicit Attack Requirement (AT:P) - the attacker must be able to reach the specific configured channel - and impact limited to high confidentiality (VC:H) with only low integrity and no availability effect (VI:L/VA:N), consistent with read-only tool exposure rather than code execution. SSVC frames it as poc / automatable=yes / partial technical impact, and a public advisory exists from VulnCheck, so exploitability is real and scriptable. Against that, EPSS is only 0.08% (23rd percentile) and it is not KEV-listed, indicating no observed widespread exploitation. Net: a genuine confidentiality-exposure priority for anyone running OpenHarness with a reachable channel on insecure defaults, but the low deployment footprint and read-only impact ceiling keep aggregate real-world risk moderate rather than critical. The AT:P requirement is the key limiter - exploitation depends on the attacker reaching the channel, which for closed messaging platforms may require knowing/joining the channel. |
| Exploit ScenarioDerived | An operator enables an OpenHarness Telegram (or Slack/Discord/Feishu) channel on a vulnerable version, accepting the default allow_from = ["*"]. An attacker who can reach that channel sends messages that pass admission as an implicitly trusted identity, then invokes default-enabled read-only tools to read files from the host running the agent runtime. Public POC/advisory material from VulnCheck describes the technique, and the automatable=yes SSVC rating means the admission bypass can be scripted. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 24, 2026
Unauthorized remote access in HKUDS OpenHarness (all versions prior to the PR #147 fix, released as v0.1.7) stems from an insecure default where every enabled remote channel is created with allow_from = ["*"], so any sender able to reach the channel passes the admission check without being an approved identity. Once past admission, an attacker reaches host-backed agent runtimes and can invoke the default-enabled read-only tools, enabling unauthorized file disclosure and read access on the host. Publicly available exploit code exists (SSVC 'poc') but it is not on CISA KEV, and EPSS is very low at 0.08%.
RemediationAI
Vendor-released patch: upgrade to OpenHarness v0.1.7 or later (which merges PR #147 at commit fab40c6eabfb15f2bdf23cddd3cfe66a64ea203d), where allow_from now defaults to an empty deny-all list and enabling a channel no longer implicitly trusts all senders. If you cannot upgrade immediately, edit gateway.json and explicitly set each channel's allow_from to the specific approved user/chat IDs (for example "allow_from": ["123456"]) instead of ["*"]; an empty list denies all remote access, so use that to fully close a channel until identities are vetted - the trade-off is that legitimate users must be enumerated and any omitted ID is blocked. As a stronger compensating control, disable any remote channel that is not strictly required, and restrict network reachability to the gateway so only trusted senders can connect to the configured channel. Advisory and patch URLs: https://github.com/HKUDS/OpenHarness/pull/147 and https://www.vulncheck.com/advisories/hkuds-openharness-insecure-default-remote-channel-allowlist.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenHarness is an agent/harness gateway (the 'ohmo' CLI plus the openharness library) that bridges remote messaging channels - Telegram, Slack, Discord, Feishu - to host-backed AI agent runtimes exposing tools such as file readers. Admission control for each channel is governed by an allow_from allowlist of user/chat IDs. The root cause is CWE-276 (Incorrect Default Permissions): in src/openharness/config/schema.py the ProviderConfigs.allow_from field defaulted to Field(default_factory=lambda: ["*"]), and the ohmo CLI likewise defaulted the prompt to '*', so simply enabling a channel implicitly trusted every remote sender. The channel manager even raised a SystemExit forcing operators away from an empty (deny-all) list toward ["*"], reinforcing the insecure posture. CPE cpe:2.3:a:hkuds:openharness identifies the single affected application.
Know when Openharness gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable with no auth (PR:N) but the attacker must reach the specific channel, mapping AT:P to AC:H; impact is high confidentiality read access with only minor integrity and no availability effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3DescriptionCVE.org
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.
Executive ViewAI
HKUDS OpenHarness versions prior to v0.1.7 contain an insecure default configuration that allows any remote sender to access the host without credentials, enabling unauthorized file disclosure through default-enabled read-only tools. Organizations running affected versions expose sensitive host files to network-based attackers. This requires immediate patching to prevent data exfiltration.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Openharness
View allRemote code execution in HKUDS OpenHarness allows authenticated remote attackers to execute arbitrary operating system c
Remote command injection in OpenHarness gateway handler allows authenticated remote chat users to execute administrative
Remote attackers can install and activate arbitrary plugins in HKUDS OpenHarness through exposed plugin management comma
Remote unauthenticated attackers can bypass path restrictions in OpenHarness (pre-commit bd4df81) to read arbitrary sens
Improper access control in OpenHarness (prior to commit 166fcfe) allows local authenticated attackers with influence ove
Server-Side Request Forgery in OpenHarness AI agent framework (pre-commit bd4df81) permits remote unauthenticated attack
Cross-session information disclosure in HKUDS OpenHarness ohmo gateway allows admitted remote senders to invoke /resume
Path traversal in OpenHarness allows authenticated gateway users with chat access to read arbitrary files on the server
Remote prompt injection in OpenHarness allows low-privileged messaging channel participants to persistently corrupt AI a
Session key derivation in HKUDS OpenHarness prior to PR #159 fails to verify sender identity in shared chat/thread scope
EUVD-2026-24505
GHSA-564h-hx6x-wg47
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB