Quick answers
- Is CVE-2026-40503 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40503 being exploited in the wild.
- How severe is CVE-2026-40503?
- Medium severity, with a CVSS score of 6.5, published 16 April 2026.
- Which products and versions are affected?
- HKUDS OpenHarness Prior to commit dd1d235450dd987b20bff01b7bfb02fe8620a0af.
- Is there a fix for CVE-2026-40503?
- A patch was published on 2026-04-13: Fix merged into main branch in commit dd1d235 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40503 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-40503?
- Check whether you run HKUDS OpenHarness at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in OpenHarness due to insufficient input validation in the '/memory show' slash command. The application joins attacker-controlled path parameters with the project memory directory without verifying that the resulting path remains within the intended directory boundaries. A remote attacker with chat access can provide traversal sequences (e.g., ../../) to escape the project memory directory and read arbitrary files accessible to the OpenHarness process. The issue was addressed in commit dd1d235 by enforcing filesystem containment and hardening the gateway's slash command security model.
Affected products
- HKUDS OpenHarness Prior to commit dd1d235450dd987b20bff01b7bfb02fe8620a0af
Timeline
- 2026-04-12: disclosed: Initial pull request submitted by researcher
- 2026-04-13: patched: Fix merged into main branch in commit dd1d235
- 2026-04-16: advisory: CVE published to NVD