Which versions of Openharness are affected by CVE-2026-40503?

OpenHarness contains a path traversal vulnerability affecting all versions before commit dd1d235 that allows authenticated gateway users with chat access to read arbitrary files from the server,…. A patch is available.

How to fix or mitigate CVE-2026-40503?

Within 24 hours: identify all OpenHarness deployments in your environment and document current versions. Within 7 days: apply vendor patch by updating to commit dd1d235450dd987b20bff01b7bfb02fe8620a0af or later, and audit gateway user access controls to restrict chat permissions to only required personnel. Within 30 days: conduct log analysis for suspicious '/memory show' command usage with directory traversal patterns and review any files that may have been accessed by untrusted users.

Openharness CVE-2026-40503

Q: What is the CVSS score of CVE-2026-40503?

CVE-2026-40503 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-23143 HIGH

Path Traversal (CWE-22)

2026-04-16 VulnCheck

Path Traversal Openharness

7.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (VulnCheck) · only source for this CVE.

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 01:45 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Apr 16, 2026 - 01:38 vuln.today

cvss_changed

Severity Changed

Apr 16, 2026 - 01:38 NVD

MEDIUM HIGH

CVSS changed

Apr 16, 2026 - 01:38 NVD

6.5 (MEDIUM) 7.1 (HIGH)

Analysis Generated

Apr 16, 2026 - 01:19 vuln.today

EUVD ID Assigned

Apr 16, 2026 - 01:15 euvd

EUVD-2026-23143

Analysis Generated

Apr 16, 2026 - 01:15 vuln.today

Patch released

Apr 16, 2026 - 01:15 nvd

Patch available

CVE Published

Apr 16, 2026 - 00:08 nvd

HIGH 7.1

DescriptionCVE.org

OpenHarness prior to commit dd1d235 contains a path traversal vulnerability that allows remote gateway users with chat access to read arbitrary files by supplying path traversal sequences to the /memory show slash command. Attackers can manipulate the path input parameter to escape the project memory directory and access sensitive files accessible to the OpenHarness process without filesystem containment validation.

AnalysisAI

Path traversal in OpenHarness allows authenticated gateway users with chat access to read arbitrary files on the server via the '/memory show' slash command. Affecting all versions prior to commit dd1d235, attackers can inject directory traversal sequences to escape the project memory directory and access any file readable by the OpenHarness process. CVSS 7.1 reflects high confidentiality impact with low-privilege network access. Vendor patch available via GitHub commit dd1d235450dd987b20bff01b7bfb02fe8620a0af. No public exploit identified at time of analysis, EPSS data unavailable.

Technical ContextAI

OpenHarness is an AI model orchestration framework (HKUDS/OpenHarness). The vulnerability stems from CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) in the slash command handler for '/memory show'. This command appears designed to retrieve project memory artifacts from a designated directory, but fails to validate or sanitize the path parameter before filesystem operations. Classic path traversal vectors like '../../../etc/passwd' can be injected to navigate outside the intended directory boundary. The affected component processes user-supplied path input without canonicalization, allowing relative path sequences to resolve to arbitrary filesystem locations within the process permission scope. This affects the cpe:2.3:a:hkuds:openharness product across all pre-patch versions.

RemediationAI

Vendor-released patch: commit dd1d235450dd987b20bff01b7bfb02fe8620a0af on GitHub (https://github.com/HKUDS/OpenHarness/commit/dd1d235450dd987b20bff01b7bfb02fe8620a0af). Upgrade OpenHarness to any version containing this commit or later by pulling the latest code from the main branch and rebuilding. Review GitHub Pull Request #127 (https://github.com/HKUDS/OpenHarness/pull/127) for implementation details. If immediate patching is not feasible, implement compensating controls: (1) Run the OpenHarness process with a dedicated least-privilege service account that has read access ONLY to necessary directories, preventing traversal to sensitive system files - verify permissions exclude /etc, /root, credential stores; (2) Restrict chat access authentication to trusted users only, reducing the authenticated attacker pool; (3) Deploy filesystem-level access controls (AppArmor, SELinux) to confine the OpenHarness process to its working directory; (4) Monitor filesystem access logs for suspicious read patterns outside expected paths. Note that restricting chat access does not eliminate the vulnerability for authorized users who may be compromised or malicious insiders.