CVE-2026-44843 LangChain: Unsafe deserialization of attacker-controlled LangChain objects through overly broad `load()` allowlists

High 8.2 Published Updated

Attackers can instantiate trusted LangChain classes with untrusted arguments via overly broad deserialization allowlists, potentially leading to code execution.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-44843?

CVE-2026-44843 is a high-severity unsafe deserialization vulnerability in langchain-ai langchain, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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 trusted runtime paths to instantiate classes with untrusted constructor arguments. This vulnerability is fixed in 0.3.85 and 1.3.3.

Weakness: CWE-502

Which versions are affected by CVE-2026-44843?

5 open source packages ship an affected version, including langchain-core. It affects 1 product.

PackageAffectedFixed in
langchain-core PyPIAll versions0.3.85, 1.3.3
langchain-core PyPIAll versions0.3.85
langchain-core PyPIAll versions0.3.85
langchain-core PyPIFrom 1.0.01.3.3
langchain-core PyPIFrom 1.0.01.3.3

Products include Langchain Langchain.

How do I fix CVE-2026-44843?

Upgrade langchain-core to a fixed version for your release line: 0.3.85 or 1.3.3.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-44843 being exploited?

There is no known exploitation of CVE-2026-44843 in the wild and no public exploit code.

Sources

Also known as CLSA-2026-1781571263, ECHO-6a00-8440-c5ae, GHSA-pjwx-r37v-7724, PYSEC-2026-2564, ROOT-APP-PYPI-CVE-2026-44843.

Is CVE-2026-44843 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free