CVE-2026-115885: CWE-532: Insertion of Sensitive Information into Log File in langchain-ai langgraph
Description
A vulnerability in langgraph CLI versions from 0.4.15 up to but not including 0.4.32 causes sensitive temporary registry push tokens to be logged in verbose mode. This token exposure allows anyone with access to CI logs or terminal recordings to pull or push images to the deployment's image repository within the token's 12-hour validity. The issue does not affect deployments without verbose mode or remote image builds and does not allow updating deployments to execute pushed images. The vulnerability is fixed in version 0.4.32.
CVSS v4.0
Score 4.1medium
Affected software
langchain-ai
langgraph
pkg:github/langchain-ai/langgraphRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The LangGraph CLI (langgraph) versions >=0.4.15 and <0.4.32 have a CWE-532 vulnerability where the 'langgraph deploy --verbose' command passes a temporary registry push token via standard input to 'docker login --password-stdin'. However, the CLI subprocess helper prints this command input in verbose mode, causing the token to be logged. This exposure allows an attacker who can read CI logs or terminal recordings to use the token to pull or push images to the deployment's image repository during the token's maximum 12-hour lifetime. The token alone cannot update deployments to execute pushed images. Deployments without verbose mode and remote image builds are not affected. The vulnerability is resolved in langgraph version 0.4.32.
Potential Impact
Exposure of temporary registry push tokens in logs or terminal recordings can lead to unauthorized image repository access, allowing attackers to pull or push container images within the token's validity period (up to 12 hours). This could compromise the integrity of deployment images. However, the token does not permit updating deployments to execute pushed images, limiting the scope of impact. Deployments not using verbose mode or remote image builds are unaffected.
Mitigation Recommendations
Upgrade langgraph to version 0.4.32 or later, where this logging of sensitive tokens in verbose mode is fixed. Avoid using the '--verbose' flag during deployment until the update is applied. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-23T19:37:27.176Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6adbd340d73cc49347c1eff3
Added to database: 10/23/2026, 21:36:00 UTC
Last enriched: 10/23/2026, 21:50:23 UTC
Last updated: 10/23/2026, 21:50:50 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.