Unauthorized host file access via wildcard channel allowlist
Published Apr 21, 2026 · Updated Apr 21, 2026
Insecure default permissions in HKUDS OpenHarness before 0.1.7 allow remote attackers to access host-backed agent runtimes. BaseChannelConfig initializes enabled remote channels with a wildcard allow_from list, while the configuration wizard preserves that value and ChannelManager rejects an empty deny-all list. An operator must enable a reachable remote channel; any sender on that channel then passes admission and can invoke default read-only tools to read host files.
Summary
What happened
Insecure default permissions in HKUDS OpenHarness before 0.1.7 allow remote attackers to access host-backed agent runtimes. BaseChannelConfig initializes enabled remote channels with a wildcard allow_from list, while the configuration wizard preserves that value and ChannelManager rejects an empty deny-all list. An operator must enable a reachable remote channel; any sender on that channel then passes admission and can invoke default read-only tools to read host files.
The record
- CVE
- CVE-2026-6823
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Data Intelligence Lab @ HKU
- Product
- OpenHarness
- Classifications
- CWE-276, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <PR #147
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Pull request 147 safe reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo