langgraph-api implements the LangGraph API for rapid development and testing. Prior to 0.10.0, the langgraph-api run-creation path authorizes the assistant attached to a run by dispatching assistants.search with an incomplete value instead of the assistants.read event used by direct reads and cron creation. In deployments with custom resource handlers that register only assistants.read, omit an assistants.search handler, and have no global fallback handler, no applicable handler supplies an owner filter, allowing a low-privileged user to reference another user's private assistant through POST /runs or POST /threads/{thread_id}/runs. The run-creation response can disclose the private assistant's metadata, config, and context, and the run can execute using that assistant's configuration. Deployments without custom authorization handlers, or with an equivalent owner filter applied through a global handler or across all assistant events, are not affected. This issue is fixed in version 0.10.0.
CVE-2026-55236
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (15th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 15th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 19, 2026
Last Modified
September 30, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026docs/src/langsmith/agent-server-changelog.mdx at 7b70fbacab21f84d9c6f9848f86cdeb471adbb50 · langchain-ai/docs · GitHub
https://github.com/langchain-ai/docs/blob/7b70fbacab21f84d9c6f9848f86cdeb471adbb50/src/langsmith/agent-server-changelog.mdxIncomplete assistant authorization in LangGraph Server run creation · Advisory · langchain-ai/helm · GitHub
https://github.com/langchain-ai/helm/security/advisories/GHSA-jfj5-wrj9-63x4Vendor Advisories for CVE-2026-55236(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| langgraph-api | 0.0.1 ... 0.9.1 (410 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 36× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 19:28 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 21:36 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 22:46 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 20:04 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 08:42 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-29 02:43 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-28 04:51 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 06:53 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 00:50 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 01:27 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 03:36 UTCEG score recompute
- 2026-09-22 05:44 UTCEG score recompute
- 2026-09-21 07:53 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
Show 12 moreShow fewer
- 2026-09-20 09:07 UTCEG score recompute
- 2026-09-19 10:14 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 11:02 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:33 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 17:55 UTCEG score recompute
- 2026-09-14 16:45 UTCEG score recompute
- 2026-09-14 16:26 UTCEG score recompute
- 2026-08-19 19:42 UTCEG score recompute
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-55236?
When was CVE-2026-55236 disclosed?
Is CVE-2026-55236 actively exploited?
What is the CVSS score of CVE-2026-55236?
How do I remediate CVE-2026-55236?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55236
Is Your Infrastructure Affected by CVE-2026-55236?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.