Critical Sandbox Escape Vulnerability in DeepSeek Harness Lets AI Agents Disable Protections with One Command
Security researchers from OX Research have disclosed a high-severity vulnerability in DeepSeek Harness, an open-source framework designed to let AI agents safely work with code and files on a developer’s local machine.
The flaw, assigned CVE-2026-82533 and rated 9.4 out of 10, enabled an AI agent to disable its own protective sandbox using a single command. In normal operation, the sandbox prevents the agent from writing data outside its designated working directory and requires explicit user confirmation for sensitive actions.
By sending a request to the tool’s local web interface, the agent could switch its active session into danger-full-access mode. This change instantly removed all write restrictions and eliminated confirmation prompts. The attack could be initiated via prompt injection: an adversary would embed a malicious instruction inside a file or other content that the agent later analyzed.
The web interface did not require any authentication. Trust decisions were based solely on the Host header, which an attacker could spoof. In addition, the interface address and current session identifier were automatically passed into the agent’s environment variables, making exploitation straightforward.
The vulnerability impacted all versions up to and including 0.1.1-rc.2. A fix was published on GitHub on 27 August, with the first protected npm release being 0.1.2-alpha.2. The current stable build, 0.1.2-rc.1, also contains the patch. Developers are advised to update at minimum to 0.1.2-alpha.2 and to audit any third-party wrappers that embed Harness.
When an update is not feasible, users should disable the web interface entirely and remove any proxies, tunnels, or port forwards that expose it. Researchers also noted that the same unauthenticated interface could be used to download logs of every stored conversation.
DeepSeek had previously stated that its sandbox and confirmation mechanisms do not provide complete isolation, underscoring the need for additional hardening when running AI agents with local system access.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.