Skip to content
MediumVulnerability

GHSA-jfj5-wrj9-63x4: langgraph-api: Incomplete assistant authorization in LangGraph Server run creation

Published
Record updated
View JSON
Affected
  • langgraph-api < 0.10.0
Fixed in
0.10.0
  • released June 11, 2026, 69 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.3%

Summary

In affected versions of `langgraph-api`, run creation checked assistant authorization with an incomplete `assistants.search` event rather than `assistants.read`. In deployments whose custom handlers register only an `assistants.read` handler, no handler ran on that path and the owner constraint was dropped, so a run could reference another user's private assistant. The response then returned that assistant's `metadata`, `config` and `context`. The source reports no evidence of exploitation in the wild.

Mitigation

Fixed in `langgraph-api` 0.10.0. Run and cron creation now dispatch the `assistants.read` event, and client-supplied metadata is no longer forwarded into it. Deployments with custom handlers should register an `assistants.read` handler (or a global handler) that returns an owner-style filter, confirm parity across the read, search and run/cron creation paths, and move any logic that read or stamped the metadata field on that event into the run/cron create handlers.