CVE-2026-55236
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 6% of all known CVEs.
References
Related Vulnerabilities
Other CWE-285 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-29927 | Critical | 9.1 | 99% | - | Fix |
| CVE-2023-32707 | High | 8.8 | 79% | - | Fix |
| CVE-2021-28799 | Critical | 10.0 | 78% | KEV + Ransom | Fix |
| CVE-2023-48241 | High | 7.5 | 73% | - | Fix |
| CVE-2023-22480 | High | 7.3 | 67% | - | Fix |
| CVE-2022-3229 | Critical | 9.8 | 66% | - | - |
Common questions
How do I fix CVE-2026-55236?
No published fix for CVE-2026-55236 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55236 being actively exploited?
Not that we know of. CVE-2026-55236 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.16% is the estimated probability that it will be exploited in the next 30 days. That is higher than 6% of all scored CVEs.
How severe is CVE-2026-55236?
CVE-2026-55236 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55236
Markdown
[](https://tridentstack.com/cve/CVE-2026-55236)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55236"><img src="https://tridentstack.com/cve/badge/CVE-2026-55236.svg" alt="CVE-2026-55236"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-14.