CVE-2026-115885: LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output
Affects langgraph-cliSource GCVE Database
Not known to be exploited · CVSS 4.1 Medium : upgrade to 0.4.32 when convenient.
Data as of 28 Oct 2026, 22:12 UTC
- Patch
- Available – fixed in 0.4.32
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade langgraph-cli to 0.4.32.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIlanggraph-cli | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- github.com/langchain-ai/langgraph/security/advisories/GHSA-8prr-f582-jqq3 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-115885 (opens in a new tab)
- github.com/langchain-ai/langgraph/pull/8482 (opens in a new tab)
- github.com/langchain-ai/langgraph/commit/1afaca35a0d4962fb0203a0e9133a07ffd6a553c (opens in a new tab)
- github.com/langchain-ai/langgraph (opens in a new tab)
- github.com/langchain-ai/langgraph/releases/tag/cli%3D%3D0.4.32.dev0 (opens in a new tab)