# CVE-2026-112346: OpenHands Software Agent SDK < 1.52.0 Unauthenticated Sandbox Agent Server RCE


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-rp7h-crm7-h5qj

## What is CVE-2026-112346?

CVE-2026-112346 is a critical vulnerability in OpenHands Software Agent SDK, published on 26 Oct 2026. 

### Official description

OpenHands Software Agent SDK before 1.52.0 contains an unauthenticated remote code execution vulnerability where the DockerWorkspace and Apptainer workspace launchers bind the sandbox agent server to all network interfaces (0.0.0.0) with an empty session_api_keys list, disabling authentication by default. Attackers who can reach the published container port can send unauthenticated HTTP and WebSocket requests to execute arbitrary shell commands as root in the sandbox, access the mounted workspace, and read plaintext secrets from the secrets store.

Weakness: CWE-1327 (Binding to an Unrestricted IP Address)

## Which versions are affected by CVE-2026-112346?


## How do I fix CVE-2026-112346?

No fix has been published for CVE-2026-112346 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112346 being exploited?

There is no known exploitation of CVE-2026-112346 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112346 and fix it if it is affected.

What it is: CVE-2026-112346 is a critical vulnerability in OpenHands Software Agent SDK, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112346 in the wild and no public exploit code.

Affected product: OpenHands Software Agent SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112346/ (Markdown: https://insights.sbomify.com/CVE-2026-112346/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112346
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112346
- OSV: https://osv.dev/vulnerability/CVE-2026-112346

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112346/
Summaries are generated and may contain mistakes; the official description above is the record.