Skip to main content
← All vulnerabilities
CVE-2026-115885EUVD-2026-109183GHSA-8PRR-F582-JQQ3

LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 0.4.32
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

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.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original 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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • langchain-ai langgraph

    From 0.4.15 · fixed in 0.4.32

  • langgraph-cliPyPI

    From 0.4.15 · fixed in 0.4.32

References 4

GitHub · langchain-ai/langgraph