CVE-2026-34070: LangChain Core has Path Traversal vulnerabilites in legacy `load_prompt` functions
LangChain is a framework for building agents and LLM-powered applications. Prior to version 1.2.22, multiple functions in langchain_core.prompts.loading read files from paths embedded in deserialized config dicts without validating against directory traversal or absolute path injection. When an application passes user-influenced prompt configurations to load_prompt() or load_prompt_from_config(), an attacker can read arbitrary files on the host filesystem, constrained only by file-extension checks (.txt for templates, .json/.yaml for examples). This issue has been patched in version 1.2.22.
Security readout for executives and security teams
Plain-English summary
CVE-2026-34070 lets a malicious user-influenced LangChain prompt configuration make an application read unintended local files. The impact is data exposure, not code execution, but secrets or configuration files could be exposed if the vulnerable loading functions are reachable.
Executive priority
Treat as high priority for AI applications that accept external prompt configuration. The business risk is unauthorized file disclosure from application hosts, especially where secrets or customer data are present.
Technical view
Before version 1.2.22, langchain_core.prompts.loading functions load_prompt() and load_prompt_from_config() accepted paths from deserialized config dictionaries without preventing directory traversal or absolute path injection. Reads are constrained by extension checks for templates and examples, but confidentiality impact is rated high.
Likely exposure
Exposure is likely limited to applications using affected LangChain versions before 1.2.22 and passing user-influenced prompt configurations into load_prompt() or load_prompt_from_config().
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Abuse requires a reachable application path where attacker-controlled or attacker-influenced prompt configuration is deserialized and loaded.
Researcher notes
Focus review on trust boundaries around prompt configuration deserialization. Extension checks reduce some paths but do not eliminate sensitive file disclosure risk for allowed .txt, .json, .yaml, or .yml-style prompt resources if reachable.
Mitigation direction
Upgrade LangChain or langchain-core to version 1.2.22 or later.
Stop passing user-influenced prompt configurations to legacy prompt loading functions.
Restrict prompt file loading to approved directories and trusted configuration sources.
Review Red Hat advisories if consuming LangChain through Red Hat products.
Check vendor guidance for any additional downstream fixes or backports.
Validation and detection
Inventory deployed LangChain and langchain-core versions across applications.
Identify use of load_prompt() and load_prompt_from_config().
Trace whether prompt configurations can be influenced by users or external systems.
Confirm upgraded packages include the 1.2.22 fix or downstream backport.
Review logs for unexpected prompt file-loading failures or unusual configuration inputs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.