[etserend]

Summary

Fixes CVE-2026-104873 in langgraph-sdk (fixed in 0.4.4): updates the locked version from 0.4.2 to 0.4.8, the latest 0.4.x release.

From 0.1.45 until 0.4.4, the resource-scoped authorization decorators @auth.on.threads, @auth.on.assistants and @auth.on.crons in langgraph_sdk.auth ignore the actions argument and register the handler for every action on the resource. An authenticated user of a LangGraph API server that relies on those decorators could bypass fallback permission checks.

splunk-ao does not use langgraph_sdk.auth or run a LangGraph API server. langgraph-sdk is only a transitive dependency of langgraph, which is imported by the LangChain handler and serialization code (optional langchain/all extras).

Changes

• poetry.lock: langgraph-sdk 0.4.2 -> 0.4.8. No other package changes, pyproject.toml is untouched. langgraph requires langgraph-sdk >=0.4.2,<0.5.0, so the new version is within the existing constraint.

Test plan

• poetry check --lock: passes; poetry update langgraph-sdk --lock changes only langgraph-sdk, content-hash unchanged
• In a scratch environment built from this lock (Python 3.13, langgraph 1.2.9, langchain-core 1.5.0), the langgraph-related test files (test_attribute_mapping, test_base_handler, test_langchain, test_langchain_async, test_langchain_middleware, utils/test_serialization): 288 passed, 3 skipped with langgraph-sdk 0.4.8, identical to 0.4.2
• Import smoke test of langgraph.graph, langgraph.types, langgraph_sdk and langgraph_sdk.auth with 0.4.8
• CI

Not verified: the full unit suite and type-check were not re-run for this lock-only change. The default development environment does not install langgraph, so the standard suite does not exercise it; that is why the targeted run above used a scratch environment.

Examples

examples/agent/startup-simulator-3000/requirements.txt (langgraph-sdk==0.1.70) and examples/agent/langgraph-fsi-agent/before/poetry.lock (0.1.72) are not changed here. langgraph-sdk 0.4.4 and later require langchain-core>=1.4.0, and those examples pin langchain-core 0.3.x and langgraph 0.4.x, so fixing them is a major langchain/langgraph migration of the example apps, not a pin bump. Neither example uses langgraph_sdk.auth.

🤖 Generated with Claude Code

[etserend]

🤖 This review was generated by the Astra agent (claude-opus-5-5). It may contain mistakes.

Verdict: approve — The lock-only bump moves langgraph-sdk to 0.4.8, past the 0.4.4 fix, and stays inside langgraph's constraint. The resolved dependencies are consistent.

Follow-ups

Suggested follow-up work that could be tracked as Jira tickets:

• examples/agent/langgraph-fsi-agent/before/poetry.lock:1-1: This example lock still pins langgraph-sdk 0.1.72. examples/agent/startup-simulator-3000/requirements.txt still pins 0.1.70. Both versions are in the CVE-2026-104873 range. The PR description says that fixing them needs a langchain-core 1.x and langgraph 1.x migration. Track that migration in its own ticket, because FOSSA can flag these manifests separately.