Skip to content
MediumVulnerability

GHSA-2c9q-c2q9-qgqv: langgraph-api: Relative webhook targets in LangGraph Server can reach in-process routes without authentication

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.4%

Summary

In affected versions of langgraph-api (the LangGraph Server runtime), a run or cron created with a relative webhook target was delivered through an in-process loopback transport that the authentication middleware treats as internal and does not authenticate. This let such requests reach thread and run routes without the usual authentication context, so in deployments that scope data by owner, one user could create a run on or modify another user's thread, and limited thread metadata could appear in the created run record.

Mitigation

Fixed in langgraph-api 0.10.0, which denies loopback webhook delivery by default via the webhooks.url.disable_loopback policy (defaults to enabled), covering relative targets, localhost-style hostnames, loopback address ranges and hostnames resolving into the loopback range. Deployments needing same-process webhook delivery can set webhooks.url.disable_loopback: false in langgraph.json (or the equivalent LANGGRAPH_WEBHOOKS configuration), only when they control the routes those webhooks reach, since delivery is unauthenticated. Operational guidance: upgrade to a release containing this change, keep loopback delivery disabled unless required, and if enabled, restrict it to routes you control and apply authorization within those routes.