What is vulnerability CVE-2026-112346 in OpenHands Software Agent SDK?

What is vulnerability CVE-2026-112346 registered in the OpenHands Software Agent SDK? It is a critical unauthenticated remote code execution (RCE) flaw affecting SDK versions prior to 1.52.0 critical vulnerability details CVE-2026-110447 in Collabora Online within Nextcloud. This issue arises due to a misconfiguration in the DockerWorkspace and Apptainer workspace launchers.

During default operation, the sandbox agent server binds to all available network interfaces (0.0.0.0) while maintaining an empty list of session_api_keys. This completely disables any authentication mechanism, allowing any external actor with network access to interact directly with the system.

Who does it affect and what risks does this critical RCE flaw entail?

Who is affected by this security flaw cataloged with a CVSS score of 9.8? The issue directly impacts all developers and infrastructure environments using SDK versions prior to 1.52.0 employing Docker or Apptainer containers We analyze the critical vulnerability CVE-2026-115905 with CVSS 10.0 in the Rust zip library.

Any attacker who manages to reach the published port of the container can send HTTP and WebSocket requests entirely free of authentication. This enables arbitrary execution of shell commands with root privileges inside the sandbox, further facilitating access to the mounted workspace and reading stored plain text secrets.

How do I protect myself?

How do I protect myself and mitigate this security breach in production environments? Developers must apply the official guidelines published in the repository to secure affected services using the corresponding Technical Reference patch.

To resolve the incident permanently, it is necessary to follow a series of steps to update and validate the container environment.

  1. Update the OpenHands Software Agent SDK package to version 1.52.0 or higher using your usual dependency manager.
  2. Verify that the official repository includes the patch changes in the corresponding Technical Reference commit.
  3. Review the official release notes to confirm resolution of the Technical Reference issue.
  4. Check additional details in the VulnCheck security advisory to validate Technical Reference network configurations.