LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning
CVE-2026-45134 · GHSA-3644-q5cj-c5c7 · published 2026-05-13 · updated 2026-06-08
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.20%
- Fixed in
- 0.8.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An attacker who publishes a malicious prompt to LangSmith Hub may be able to affect applications that pull that prompt by owner/name. If the prompt manifest reaches the SDK's deserialization path, the SDK will instantiate the referenced LangChain objects with the attacker-supplied constructor arguments rather than treating the manifest as inert data. Realistic impacts include: Server-side request forgery (SSRF), outbound request redirection, and interception of LLM traffic if a prompt manifest configures an LLM client with an attacker-controlled base_url, proxy, or equivalent endpoint-setting parameter. …
Upgrade langsmith to 0.8.0 or later, and langchain to 0.3.30 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The LangSmith SDK now blocks pulling public prompts by owner/name by default. Callers must explicitly opt in by passing dangerously_pull_public_prompt=True (Python) or dangerouslyPullPublicPrompt: true (JS/TS) to acknowledge the trust boundary. This flag should only be set after reviewing and trusting the prompt contents, not merely the publishing account. Upgrade to LangSmith SDK Python >= 0.8.0 or JS/TS >= 0.6.0.
- CriticalLMDeploy has Remote Code Execution by Pickle Deserialization via handle_zmq_recv in lmdeploy/lmdeploy/pytorch/disagg/conn/engine_conn.pylmdeploy
- CriticalLMdeploy has Remote Code Execution by Pickle Deserialization via zmq_rpc.call_and_response() in InterLM/lmdeploylmdeploy
- CriticalSGLang: Unauthenticated RCE via --enable-custom-logit-processorsglang
- CriticalSGLanG: Multimodal scheduler deserializes untrusted pickle data on 0.0.0.0 ROUTER socketsglang
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- CriticalLangchain SQL Injection vulnerabilitylangchain
- CriticalLangchain vulnerable to arbitrary code execution via the evaluate function in the numexpr librarylangchain
- Criticallangchain vulnerable to arbitrary code executionlangchain
- CriticalLangChain vulnerable to arbitrary code executionlangchain
- CriticalLangChain vulnerable to arbitrary code executionlangchain
- CriticalLangChain vulnerable to arbitrary code executionlangchain
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.