CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-44843 remediation guide

langchain-ai langchain

LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.85 and 1.3.3, LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call load() with allowed_objects="all". This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause...

Open CVE record
Productlangchain-ai langchain
Affected versions>= < 0.3.85, >= >= 1.0.0a1, < 1.3.3, < 0.3.85, >= 1.0.0 < 1.3.3
Fixed versions0.3.85, 1.3.3
Priority basisReview · CVSS 8.2 · EPSS 0.41%
01

Identify the affected asset

Confirm whether langchain-ai langchain is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 0.3.85, >= >= 1.0.0a1, < 1.3.3, < 0.3.85, >= 1.0.0 < 1.3.3. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 0.3.85, 1.3.3. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.