AIKIDO-2026-944829
langsmith is vulnerable to Exposure of Sensitive Information
57
Medium Risk
This Affects:
langsmithTL;DR
The langsmith SDK builds trace run metadata with get_langchain_env_var_metadata(), which collects every LANGCHAIN_ and LANGSMITH_ prefixed environment variable except a small excluded set and names containing key, secret, or token. The control-plane signing secrets LANGSMITH_SIGNING_JWKS and LANGSMITH_SANDBOX_CALLBACK_SIGNING_JWK contain none of those substrings, so they are attached to every traced run. On self-hosted and BYOC deployments these Ed25519 signing private keys are forwarded into LangSmith trace metadata, exposing them to anyone able to read the traces. The fix adds both variable names to the excluded set so they are kept out of run metadata.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and your deployment injects the LANGSMITH_SIGNING_JWKS or LANGSMITH_SANDBOX_CALLBACK_SIGNING_JWK environment variables.
Background info
langsmith is vulnerable to Exposure of Sensitive Information in versions 0.1.46 - 0.10.8.
How to fix this
Upgrade the langsmith library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant