cve.bz

CVE-2026-44843 langchain langchain: Deserialization of Untrusted Data

8.2 highEPSS 0.4%Fix available

High (8.2) in langchain langchain. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in langchain-core 0.3.85, 1.3.3.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-44843 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-44843?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-44843?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-44843 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
langchain:langchainbefore 0.3.85
langchain:langchainfrom 1.0.0 before 1.3.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pjwx-r37v-7724PyPIlangchain-core>=1.0.0 <1.3.31.3.3
GHSA-pjwx-r37v-7724PyPIlangchain-core<0.3.850.3.85
PYSEC-2026-2564PyPIlangchain-core<0.3.85
>=1.0.0 <1.3.3
0.3.85, 1.3.3

Red Hat

Red Hat rates this Important.

Red Hat's statement

This Important vulnerability in LangChain allows a remote attacker to achieve information disclosure and partial data integrity compromise. The flaw arises from overly broad object allowlists in older runtime code paths, which can deserialize attacker-controlled payloads and instantiate classes with untrusted arguments. Red Hat products integrating LangChain are affected if they process untrusted structured input and utilize deprecated APIs such as RunnableWithMessageHistory, astream_log(), or astream_events(version="v1"), potentially leading to prompt injection or sensitive data exposure.

Red Hat's mitigation

To mitigate this issue, applications using LangChain should avoid passing untrusted structured input directly to load() or loads() functions. Instead, ensure all incoming untrusted data is validated and canonicalized into an inert schema before being processed by LangChain. Additionally, migrate away from deprecated LangChain APIs, including RunnableWithMessageHistory, astream_log(), and astream_events(version="v1"), as these older code paths are more susceptible to insecure deserialization.

ProductPackageStateAdvisory
Red Hat Migration Toolkit for Applications 8.2mta/mta-solution-server-rhel9:1784109883Fixed 2026-07-21RHSA-2026:43038
Red Hat OpenShift AI 3.3rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1789570674Fixed 2026-09-30RHSA-2026:73987
Red Hat OpenShift AI 3.4rhoai/odh-autorag-rhel9:1786612637Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-llama-stack-core-rhel9:1786635926Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1787330585Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.4rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:1791785804Fixed 2026-10-19RHSA-2026:84734
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Will not fix
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Will not fix
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-44843.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON