MEDIUM 6.5

CVE-2026-56695: OpenHarness ohmo Gateway Unauthorized Snapshot Access via Default Remote Invocation

OpenHarness ohmo gateway contains a configuration flaw where two slash commands—/resume and /summary—treat all authenticated users as capable of invoking remote operations by default. An attacker with legitimate access to a shared gateway channel can exploit this to discover and retrieve session snapshots belonging to other users simply by guessing or enumerating snapshot IDs. These snapshots may contain sensitive information such as system prompts, stored credentials, tool execution results, and internal file paths.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-862
Affected products
0 configuration(s)
Published / Modified
2026-06-23 / 2026-06-24

NVD description (verbatim)

OpenHarness ohmo gateway /resume and /summary slash commands default remote_invocable to True, allowing admitted remote senders to enumerate and load arbitrary session snapshots by ID. Attackers can exploit this to access victim snapshots containing private prompts, credentials, tool output, and file paths via shared gateway channels.

4 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability stems from the remote_invocable parameter defaulting to True for the /resume and /summary slash commands in OpenHarness ohmo gateway. This default configuration permits any admitted sender on a shared channel to invoke snapshot enumeration and loading operations without additional authorization checks. The attack surface includes any environment where multiple users share gateway channel access and snapshots are not isolated by role or ownership. CWE-862 (Missing Authorization) categorizes the underlying defect: the application fails to enforce object-level access controls on snapshot retrieval.

Business impact

Organizations using OpenHarness ohmo gateway for multi-user or team-based workflows face exposure of confidential information stored within session snapshots. Leaked credentials could enable lateral movement or privilege escalation within downstream systems. Exposed system prompts may reveal business logic, API integrations, or proprietary tool configurations. For regulated environments (healthcare, finance, legal), unauthorized access to snapshots containing client data or sensitive processing results creates compliance risk and potential breach notification obligations.

Affected systems

OpenHarness ohmo gateway instances with the /resume and /summary commands enabled are affected. The vulnerability applies to any deployment where multiple users share gateway channel access and session snapshots are stored. No specific product version range is provided in vendor advisories at this time; verify affected versions against OpenHarness release notes and security announcements.

Exploitability

Exploitation requires prior authentication to the gateway—an attacker cannot perform this attack from an unauthenticated state. However, the barrier to entry is low for insiders or users with legitimate (but limited) access to shared channels. Snapshot enumeration is trivial once access is obtained, as attackers need only iterate snapshot IDs or use common naming patterns. The CVSS 3.1 score of 6.5 (MEDIUM) reflects the requirement for authenticated access (PR:L) balanced against high confidentiality impact and network-based attack vector.

Remediation

Administrators should immediately audit gateway configurations and set remote_invocable to False for /resume and /summary commands unless explicitly required. Where remote invocation is necessary, implement explicit authorization policies that bind snapshot access to ownership or explicit role assignments. Additionally, review historical snapshot access logs to identify any unauthorized enumeration or retrieval during the vulnerability window. Consider enforcing channel-level access controls and segmenting user populations by sensitivity of data stored in snapshots.

Patch guidance

Check OpenHarness security advisories and release notes for patched versions that correct the default remote_invocable setting. Apply patches to all gateway instances in your environment. If patching cannot be completed immediately, apply the manual configuration workaround: disable remote invocation for these commands via gateway configuration files or environment variables, then verify the changes are in effect by testing unauthorized snapshot access attempts.

Detection guidance

Monitor gateway logs for repeated /resume or /summary command invocations with different snapshot IDs originating from the same user or session—a pattern consistent with enumeration. Alert on snapshot loads where the requesting user does not match the snapshot owner. Implement audit logging of all snapshot access and correlation of access patterns across your gateway instances. Review recent snapshot loads by privilege level to identify cross-user access anomalies.

Why prioritize this

Although this vulnerability requires prior authentication, the low effort required to exploit it post-authentication, combined with exposure of high-value information (credentials, prompts, file paths), warrants prompt remediation. The risk is amplified in environments with shared gateway channels or federated access models. Organizations should treat remediation as near-term priority, especially in regulated industries or where gateways process sensitive workloads.

Risk score, explained

The CVSS 3.1 score of 6.5 reflects a MEDIUM severity assessment: network-accessible endpoint, low attack complexity (no special conditions required once authenticated), authenticated attacker required, and high confidentiality impact with no integrity or availability impact. The score appropriately captures the insider-threat and lateral-access risk but is constrained by the authentication requirement. Real-world risk in your environment may be higher if your gateway user population is large or includes contractors with temporary access.

Frequently asked questions

Can an unauthenticated attacker exploit this vulnerability?

No. Exploitation requires prior authentication to the gateway. The attacker must be an admitted sender on a shared channel or possess valid gateway credentials. This limits the attack surface to insiders, privileged users, or accounts that have been compromised through other means.

How do I know if our OpenHarness deployment is affected?

Check your gateway configuration files for the remote_invocable setting on /resume and /summary commands. If it is set to True or is absent (defaulting to True), your deployment is affected. Cross-reference your OpenHarness version against vendor security advisories to confirm patched versions are available.

What should I do if I suspect unauthorized snapshot access?

Review gateway audit logs immediately for snapshot loads by users who do not own the snapshots. Rotate any credentials that may have been exposed in retrieved snapshots. Assess whether the snapshots contained data subject to regulatory breach notification. Consider enabling endpoint detection and response (EDR) on systems that accessed or processed data from those snapshots to detect lateral movement.

Is there a workaround if we cannot patch immediately?

Yes. Disable remote invocation for /resume and /summary by setting remote_invocable to False in your gateway configuration, then restart the service. Verify the change is in effect by attempting unauthorized snapshot access. This workaround will break legitimate remote invocation workflows, so plan a patching timeline to restore functionality long-term.

This analysis is based on vulnerability information available as of the publication date. OpenHarness advisories and version details should be verified directly with the vendor. CVSS scores reflect standardized severity assessment but do not substitute for risk assessment in your specific environment. Patch availability and version numbers must be confirmed against official OpenHarness release notes before deployment. This vulnerability requires authenticated access; assess your gateway user population and access controls to determine realistic risk in your organization. Source: NVD (public-domain), retrieved 2026-07-29. Analysis generated by SEC.co (claude-haiku-4-5).