dbcve.org
OpenhandsApplication

CVE-2026-33718

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenHands is software for AI-driven development. Starting in version 1.5.0, 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. Version 1.5.0 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenHands versions prior to 1.5.0 contain a command injection vulnerability in the `get_git_diff()` method in `openhands/runtime/utils/git_handler.py`. The `path` parameter from the `/api/conversations/{conversation_id}/git/diff` endpoint is passed unsanitized directly to a shell command, allowing authenticated attackers to inject arbitrary shell commands by crafting malicious path values.

MitigationUpgrade to OpenHands version 1.5.0 or later, which implements proper input sanitization for the path parameter before passing it to shell commands.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenhandsApplication
Affected:< 1.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenHands installation version
    Run 'pip show openhands' or check the version in your package manager, Docker image tag, or deployment configuration
    Affected if The version is below 1.5.0 (e.g., 1.4.0, 1.3.0, etc.)
  2. Locate the git_handler.py file
    Search for the file at openhands/runtime/utils/git_handler.py in your installation directory or container image
    Affected if The file exists and contains a 'get_git_diff' method that uses shell commands with the 'path' parameter
  3. Verify the API endpoint exposure
    Check if the /api/conversations/{conversation_id}/git/diff endpoint is exposed in your OpenHands deployment (check your API routing configuration or container entrypoint)
    Affected if The endpoint is accessible without additional authentication layers beyond basic conversation access
  4. Confirm shell command execution context
    Examine the git_handler.py source code for patterns like os.system(), subprocess.call(), or shell=True usage with the path parameter passed directly
    Affected if The code passes the path parameter directly to a shell command without sanitization (e.g., no input validation, no use of shell=False with argument lists)
  5. Check runtime execution permissions
    Determine if the runtime service runs with permissions allowing shell command execution (check container/process privileges and seccomp/AppArmor profiles)
    Affected if The runtime has shell execution capabilities enabled and the git handler can invoke system commands

You are affected if your OpenHands version is below 1.5.0 AND the vulnerable git_handler.py file with unsanitized path-to-shell passing exists in your deployment AND the API endpoint is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Vendor patch github.com →
Interim mitigation

Upgrade to OpenHands version 1.5.0 or later, which implements proper input sanitization for the path parameter before passing it to shell commands.

Recommended fix High confidence

1.5.0

  1. Identify the current OpenHands version in use by checking the installed package version or project dependencies
  2. Stop any running OpenHands services or containers to prevent issues during upgrade
  3. Upgrade OpenHands to version 1.5.0 using the appropriate package manager (e.g., pip install openhands==1.5.0, or pull the 1.5.0 container image)
  4. Verify the upgrade was successful by checking the installed version
  5. Restart the OpenHands service
  6. Test that the /api/conversations/{conversation_id}/git/diff endpoint functions correctly with the fix in place
Caveat Review release notes for 1.5.0 to check for any API changes or deprecations that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openhands Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data