Skip to content

OpenHands is Vulnerable to Command Injection through its Git Diff Handler

High severity GitHub Reviewed Published Mar 23, 2026 in OpenHands/OpenHands • Updated Mar 27, 2026

Package

pip openhands (pip)

Affected versions

< 1.5.0

Patched versions

1.5.0

Description

Summary

A Command Injection vulnerability exists in the get_git_diff() method at openhands/runtime/utils/git_handler.py:134. The path parameter from the /api/conversations/{conversation_id}/git/diff API endpoint is passed unsanitized to a shell command, allowing authenticated attackers to execute arbitrary commands in the agent sandbox. The user is already allowed to instruct the agent to execute commands, but this bypasses the normal channels.


Details

Vulnerable Code Path

The vulnerability flows through these files:

  1. API Endpoint (openhands/server/routes/files.py:267-277)
@app.get('/git/diff')
async def git_diff(
    path: str,  # <-- User input from HTTP request
    ...
):
    ...
    diff = await call_sync_from_async(runtime.get_git_diff, path, cwd)  # No sanitization
  1. Runtime (openhands/runtime/base.py:1231-1233)
def get_git_diff(self, file_path: str, cwd: str) -> dict[str, str]:
    self.git_handler.set_cwd(cwd)
    return self.git_handler.get_git_diff(file_path)  # Passed directly
  1. Vulnerable Method (openhands/runtime/utils/git_handler.py:10-12, 134)
# Command template with placeholder
GIT_DIFF_CMD = 'python3 /openhands/code/openhands/runtime/utils/git_diff.py "{file_path}"'

# Line 134 - VULNERABLE: User input directly interpolated
result = self.execute(self.git_diff_cmd.format(file_path=file_path), self.cwd)
  1. Shell Execution (openhands/runtime/utils/git_diff.py:25-27)
def run(cmd: str, cwd: str) -> str:
    result = subprocess.run(
        args=cmd,
        shell=True,  # <-- Enables shell metacharacter interpretation
        stdout=subprocess.PIPE,
        stderr=subprocess.PIPE,
        cwd=cwd
    )

Root Cause

The file_path parameter is directly interpolated into a shell command string using Python's .format() method without any sanitization. When this command is executed with shell=True, shell metacharacters like ", ;, and # are interpreted, allowing command injection.

Example:

  • Input: test"; id #
  • Constructed command: python3 /script.py "test"; id #"
  • Shell interprets as two commands: python3 /script.py "test" AND id

Impact

Who is Affected

  • All OpenHands deployments exposing the /api/conversations/{id}/git/diff endpoint
  • Any authenticated user can exploit this vulnerability,

Attack Capabilities

An attacker can:

  1. Execute arbitrary commands on the runtime container as root
  2. Read sensitive files including .env, API keys, source code
  3. Write arbitrary files to inject malicious code
  4. Establish reverse shells for persistent access
  5. Potentially escape the container if Docker is misconfigured

Mitigation

Users should update to the latest version of OpenHands that includes the changes from PR #13051. The fix replaces direct shell string formatting with proper argument array handling or rigorous path sanitization to prevent command chaining.

References

@raymyers raymyers published to OpenHands/OpenHands Mar 23, 2026
Published to the GitHub Advisory Database Mar 25, 2026
Reviewed Mar 25, 2026
Published by the National Vulnerability Database Mar 27, 2026
Last updated Mar 27, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(45th percentile)

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2026-33718

GHSA ID

GHSA-7h8w-hj9j-8rjw

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.