CVE Intelligence
Medium Info disclosure

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

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.

Published Oct 23, 2026 · Updated Oct 29, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.11%
ahead of 1% of scored CVEs · Oct 29, 2026
Affects
Langchain-ai
Langgraph and 1 more
CVSS base
4.1
Medium · 3 source(s)
Prioritization reference: 5.4 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Pip Langgraph-cli: fixed in version 0.4.32 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Langchain-ai Langgraph, Pip Langgraph-cli).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Langchain-ai Langgraph version >= 0.4.15, < 0.4.32 Vulnerable CVE Program (cve.org) e CISA ADP
Pip Langgraph-cli ≥ 0.4.15 and ≤ 0.4.31 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Attack requirements
Present
Privileges required
Low
User interaction
Passive
Scope
X
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.1 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
4.1 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-532 · Insertion of Sensitive Information into Log File

Other CVEs with this weakness →

EPSS over time FIRST

Oct 24, 2026 → Oct 29, 2026 · 6 reading(s) · max 0.16%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Look for anomalous data read/export volumes and access to sensitive records.
endpoint telemetry (EDR)application logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 29, 2026 · GitHub Security Advisories
  • Affected products added · pip/langgraph-cli
    Oct 29, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Awaiting Analysis
    Oct 26, 2026 · NIST National Vulnerability Database
  • Affected products added · langchain-ai/langgraph
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 23, 2026
  • CVSS changed · 4.1
    Oct 23, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 23, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 23, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 29, 2026 – Oct 29, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

6 on the record

Elsewhere on this site

Langchain-ai
every CVE for this vendor
Info disclosure
same class
CWE-532
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-118667 LangGraph: Unencoded identifiers in LangGraph SDK v3 streaming can redirect authenticated GET requests 1d
  • CVE-2026-115883 LangGraph: Namespace labels containing `.` reach other namespaces in Postgres and SQLite stores 6d
  • CVE-2026-104873 LangGraph SDK custom auth silently ignores actions= on resource decorators 27d
  • CVE-2026-71433 LangGraph: Namespace prefix matching crosses segment boundaries in Postgres and SQLite stores Aug 6, 2026
  • CVE-2026-14742 langchain-ai langgraph Task Result Cache _cache.py _freeze weak hash Jul 5, 2026
  • CVE-2026-48775 LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading Jun 16, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115885 is "LangGraph CLI prints the registry push token in `langgraph deploy --verbose` output", rated Medium. It affects Langgraph (Langchain-ai); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.1 describes technical severity. EPSS 0.11% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.