LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output
Impact
langgraph deploy --verbose printed the temporary registry push token that the CLI uses to log Docker in to the deployment's image registry. Anyone who could read that output, for example in CI logs, could use the token until it expired.
Source excerpt · OSVDeployments reference their image by digest, so a pushed image does not run unless the deployment is updated to use it, which requires a LangSmith API key with access to the deployment.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 0.4.15 before 0.4.32Ecosystem versions | 0.4.32 |
Version evidence: OSV · GHSA-8prr-f582-jqq3
View original version evidence (18 explicit versions)
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
langchain-ai · GitHub_M
langgraph
1 range
langchain-ai · GitHub_M
langgraph
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 0.4.15, < 0.4.32
Other versions: unknown
Original source description
Summary
langgraph deploy --verbose printed the temporary registry push token that the CLI uses to log Docker in to the deployment's image registry. Anyone who could read that output, for example in CI logs, could use the token until it expired.
Details
When Docker is available, langgraph deploy builds the image locally, requests a push token from LangSmith, and runs docker login --password-stdin with the token on stdin. The CLI's subprocess helper printed each command's stdin when verbose output was on, and the login step inherited --verbose, so the token was printed right after the docker login command line.
langgraph-cli 0.4.15 through 0.4.31 are affected. Starting with 0.4.32, the login step runs without verbose output. Deploys run without --verbose, and deploys that build the image remotely, never printed the token.
Impact
You may be affected if you ran langgraph deploy --verbose with an affected version and the output was kept or shared, for example in CI logs or terminal recordings. The token is short-lived (at most 12 hours) and limited to that deployment's image repository. Someone holding it before it expired could pull the deployment's images and push new images to that repository. Deployments reference their image by digest, so a pushed image does not run unless the deployment is updated to use it, which requires a LangSmith API key with access to the deployment.
Remediation
Upgrade to langgraph-cli 0.4.32 or later. 0.4.37 also stops --verbose from printing the input of any command the CLI runs. Tokens printed more than 12 hours ago have expired.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-115885View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.