Loading vulnerability…
CVE-2026-33718 is a command injection vulnerability in OpenHands, an AI-driven development platform. The issue affects the get_git_diff() method in openhands/runtime/utils/git_handler.py at or around line 134. The path parameter supplied via the /api/conversations/{conversation_id}/git/diff API endpoint is incorporated into a shell command without adequate sanitization or safe argument handling. As a result, an authenticated attacker can inject shell metacharacters or chained commands and cause arbitrary command execution inside the agent sandbox/runtime container. Although users may already be able to instruct the agent to run commands through intended product workflows, this flaw bypasses the normal control path and executes attacker-controlled commands directly through the Git diff handler. The vulnerability is fixed in version 1.5.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
.env files, API keys, credentials, and source code; writing arbitrary files; establishing reverse shells or other persistence within the runtime environment; and abusing the compromised container as a foothold. If the underlying Docker or container environment is misconfigured, the impact may extend beyond the sandbox and could potentially facilitate container escape or broader host compromise.If you can’t patch tonight, do this now.
/api/conversations/{conversation_id}/git/diff endpoint for untrusted users, and limit authenticated access to only trusted operators. Harden the runtime container by running as a non-root user, minimizing mounted secrets, removing unnecessary credentials from the environment, and enforcing strict container isolation. Monitor for suspicious shell execution, unexpected outbound connections, reverse-shell behavior, and anomalous file access within agent sandboxes. Where feasible, add server-side validation or sanitization for the path parameter and avoid invoking shell commands through string interpolation.Patch, then assume compromise.
path input in the Git diff code path. Apply the changes associated with PR #13051 and redeploy affected instances. After upgrading, rotate any secrets that may have been exposed from the runtime environment, including API keys and credentials stored in .env files or accessible source repositories.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.