NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-115885: LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output

mediumCVSS 4.0 4.1 · 3.1 5.4GHSA-8prr-f582-jqq3

langgraph-cli 0.4.15 through 0.4.31 prints the temporary registry push token in the output of langgraph deploy --verbose. Anyone who can read that output, such as in CI logs, can use the token for up to 12 hours to pull and push images in the deployment's image repository. Fixed in 0.4.32; 0.4.37 goes further.

Published Oct 28, 2026 · Analysis Nov 1, 2026

What an attacker can do

When Docker is available, langgraph deploy builds the image locally, asks LangSmith for a push token and runs docker login --password-stdin with the token on stdin. The CLI's subprocess helper prints each command's stdin when verbose is on, and the login step inherited --verbose. The token therefore appeared right after the docker login command line.

The attacker needs access to the output: a CI log reachable by many people, a shared build console, or a terminal recording. The token lives at most 12 hours and covers only that deployment's image repository. With it, someone can pull the deployment's images, which may contain application code and baked-in configuration, and push new images to that repository.

A pushed image does not run on its own. Deployments reference their image by digest, so the deployment must be updated to use it, and that needs a LangSmith API key with access to the deployment. Deploys without --verbose, and deploys that build the image remotely, never printed the token.

Who is affected

langgraph-cli 0.4.15 through 0.4.31, only when langgraph deploy was run with --verbose and Docker built the image locally. The risk is logs you kept or shared. Check the installed version:

pip show langgraph-cli

Then look in CI logs and saved terminal sessions for runs of langgraph deploy --verbose. Tokens printed more than 12 hours ago have expired.

langgraph-cli

Ecosystem
PyPI
Affected
>= 0.4.15, <= 0.4.31
Fixed in
0.4.32
Check
pip show langgraph-cli

How to fix it

Upgrade to langgraph-cli 0.4.32 or later.

pip install --upgrade "langgraph-cli>=0.4.37"

From 0.4.32 the login step runs without verbose output. The advisory adds that 0.4.37 also stops --verbose from printing the input of any command the CLI runs. Until you upgrade, run langgraph deploy without --verbose. Delete or restrict old logs that contain the docker login line, though tokens older than 12 hours are already expired.

How to tell if you were hit

Search CI logs and saved terminal output for the docker login --password-stdin line from langgraph deploy, and check whether a token follows it. Treat any such log less than 12 hours old as exposed. Check the image repository of the deployment for pushes you did not make, and compare the digest the deployment references with what you built. Check LangSmith for deployment updates that you did not make.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to C0KERNEL.

Questions

How long is the leaked token valid?

At most 12 hours, and it only works for that deployment's image repository. Tokens printed more than 12 hours ago have expired.

Can an attacker run their own image on my deployment?

Not with the token alone. Deployments reference images by digest, so running a pushed image requires updating the deployment, which needs a LangSmith API key with access to it.

Am I affected if I never used --verbose?

No. The advisory says deploys run without --verbose, and deploys that build the image remotely, never printed the token.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology