Threat
[Security]SSRF protection bypass via HTTP proxy routing in DeepSeek Harness web_fetch (dsh v0.2.1-alpha.1) · deepseek-ai/deepseek-harness · Discussion #9680
Publication date unknown · Discovered github.com
Page published
Publication date unknown · First observed: 25 Oct 2026
Coverage timeline
Single-source research — one report is available.
Why it matters
DeepSeek Harness deployments using outbound proxies may allow agent-triggered requests to bypass SSRF safeguards and reach sensitive internal services or cloud credentials.
A security report describes an SSRF protection bypass in DeepSeek Harness v0.2.1-alpha.1: web_fetch skips destination-IP validation when routing requests through a configured HTTP(S) proxy. Attacker-controlled content could use indirect prompt injection to make the agent fetch hostnames resolving to internal services or cloud-metadata endpoints, potentially exposing credentials.