Affected version
Reports that share this version, grouped in one feed.
AutoModeMiddleware evaluates the original ToolCallRequest, but an inner middleware (e.g., HumanInTheLoopMiddleware) can replace it with a protected tool call before execution, leading to policy bypass. Ordering [auto_mode, hitl] is vulnerable while [hitl, auto_mode] blocks correctly.
When ModelRouterMiddleware is composed inside ModelFallbackMiddleware, the router unconditionally replaces the fallback model with the originally selected routed model, causing the fallback model to be skipped and the same failing model to be called twice.
The `TypeSafeClassifier` input schema generation fails with `PydanticUserError` because the private recursive `_StateValue` type alias is not resolvable in the dynamically created `TypeSafeClassifierInput` model namespace. This breaks `get_input_jsonschema()`, `as_tool()`, schemaful graph serialization, and Runnable composition schema introspection.
TypeSafeClassifier from langchain-typesafe declares is_lc_serializable() True and dumpd() succeeds, but load() fails with both allowed_objects='all' and allowed_objects=[TypeSafeClassifier]. The root cause is that the serialized ID ('langchain', 'classifiers', 'typesafe', 'TypeSafeClassifier') is not present in langchain-core's deserialization mapping and the 'langchain_typesafe' namespace is not in the default valid namespaces.
langchain-typesafe's TypeSafeClassifier does not validate that the 'questions' mapping is non-empty before making an HTTP request, causing invalid API calls and a regression from previous Pydantic-based validation.
The ModelRouterMiddleware directly indexes self.models with classifier-provided choice, causing an opaque KeyError if the choice is not a configured route. This occurs for malformed or unexpected classifier responses, preventing clear error handling.
langchain-typesafe's ModelRouterMiddleware adds model_route to the agent input JSON schema even though the middleware unconditionally overwrites any caller-provided value in before_agent. This advertises an input field that is silently ignored, causing schema-driven clients to pass a route choice that has no effect.