langgraph-api@0.5.29

  • latest version

    0.20.0.dev2

  • latest non vulnerable version

  • first published

    1 years ago

  • latest version published

    20 hours ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the langgraph-api package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Authentication

    Affected versions of this package are vulnerable to Improper Authentication in the webhook delivery process. An attacker can gain unauthorized access to and modify another user's thread or run by specifying a relative webhook target, which is routed internally without proper authentication. This may also result in limited exposure of metadata from the targeted thread.

    How to fix Improper Authentication?

    Upgrade langgraph-api to version 0.10.0 or higher.

    [,0.10.0)
    • M
    Improper Authorization

    Affected versions of this package are vulnerable to Improper Authorization in the run creation process. An attacker can gain unauthorized access to sensitive assistant metadata, config, and context fields belonging to another user, and initiate runs using another user's private assistant configuration by crafting requests that exploit incomplete authorization checks. This is only exploitable if custom authorization handlers are used that register only an assistants.read handler (without an assistants.search handler and without a global fallback handler).

    How to fix Improper Authorization?

    Upgrade langgraph-api to version 0.10.0 or higher.

    [,0.10.0)
    • H
    Authorization Bypass Through User-Controlled Key

    Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via JavaScript or TypeScript custom authentication Store authorization handlers, which can return a rewritten namespace that is not carried across the runtime boundary and applied before the Store operation. An authenticated user can therefore access another user's Store namespace when a deployment relies on namespace rewriting for isolation, allowing unauthorized reads, overwrites, searches, or deletions of Store data.

    Note: This is only exploitable when the deployment uses JavaScript or TypeScript custom authentication and its Store authorization handler relies on namespace rewriting (rather than rejection) to restrict each user to their own data.

    How to fix Authorization Bypass Through User-Controlled Key?

    Upgrade langgraph-api to version 0.15.0 or higher.

    [0.1.2,0.15.0)