Threats affecting pkg:brew/langgraph-cli

### Summary The LangGraph Python SDK v3 streaming client interpolates caller-supplied `thread_id` and `assistant_id` values into request paths without encoding them at four synchronous and asynchronous call sites. Relative path segments can therefore redirect an authenticated GET request to another path on the same configured server. ### Details The affected `get_tree` and `_fetch_state` implementations build request paths from raw identifiers rather than passing each identifier through the SDK's existing `_quote_path_param` helper. HTTP path normalization can collapse values containing relative segments before dispatch while retaining the client's authentication headers. `langgraph-sdk` versions 0.4.0 through 0.4.5 are affected. The v3 stream module is not present in the 0.3.x release line. `RemoteGraph` v3 streaming in `langgraph` 1.2.3 and later is also affected when used with a vulnerable `langgraph-sdk` version. It passes `config["configurable"]["thread_id"]` into `threads.stream(...)`, and its dependency range permits affected SDK versions. ### Impact An application is affected only if it passes attacker-controlled text as a streaming `thread_id` or `assistant_id`. In that configuration, an attacker may select another readable path on the configured server and cause the SDK to return that response to the application. Through `thread_id`, the attacker can also control the query string, for example by targeting `/store/items?namespace=...&key=...`; `assistant_id` controls only the path. The affected requests are GET operations, so this issue does not provide a write primitive. The LangGraph Platform is not exposed to this issue. ### Remediation Upgrade `langgraph-sdk` to version 0.4.6 or later. The fix encodes `assistant_id` in `get_tree` and `thread_id` in `_fetch_state` with `_quote_path_param` in both synchronous and asynchronous stream modules. If you use `RemoteGraph`, also upgrade `langgraph` to version 1.2.14 or later, which requires `langgraph-sdk>=0.4.6`.

### 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.