<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 30 Oct 2026 17:56:37 +0000</lastBuildDate>
    <item>
      <title>BREW-langgraph-cli-CVE-2026-115885 — LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output</title>
      <link>https://db.gcve.eu/vuln/brew-langgraph-cli-cve-2026-115885</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: langgraph-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`langgraph deploy --verbose` printed the temporary registry push token that the CLI uses to log Docker in to the deployment&amp;#39;s image registry. Anyone who could read that output, for example in CI logs, could use the token until it expired.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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&amp;#39;s subprocess helper printed each command&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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&amp;#39;s image repository. Someone holding it before it expired could pull the deployment&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to `langgraph-cli` 0.4.32 or later. 0.4.37…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: langgraph-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`langgraph deploy --verbose` printed the temporary registry push token that the CLI uses to log Docker in to the deployment&amp;#39;s image registry. Anyone who could read that output, for example in CI logs, could use the token until it expired.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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&amp;#39;s subprocess helper printed each command&amp;#39;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.&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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&amp;#39;s image repository. Someone holding it before it expired could pull the deployment&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to `langgraph-cli` 0.4.32 or later. 0.4.37…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/brew-langgraph-cli-cve-2026-115885</guid>
    </item>
    <item>
      <title>CVE-2026-115885 — LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output</title>
      <link>https://db.gcve.eu/vuln/cve-2026-115885</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langgraph&lt;/p&gt;
&lt;p&gt;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&amp;#39;s maximum 12-hour expiration can pull deployment images or push images to that deployment&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; langchain-ai langgraph&lt;/p&gt;
&lt;p&gt;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&amp;#39;s maximum 12-hour expiration can pull deployment images or push images to that deployment&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-115885</guid>
    </item>
  </channel>
</rss>
