Advisory record · GHSA-gr75-jv2w-4656

LangChain: Path traversal and sandbox escape in LangChain file-search middleware and loaders

CVSS 5.1 MediumEPSS 0.0021 · 11th percentile

Published by the GitHub Advisory Database at 16 Jun 2026, 15:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
langchainPyPI<1.3.91.3.9
langchain-anthropicPyPI<1.4.61.4.6
Identifiers
GHSA-gr75-jv2w-4656 · CVE-2026-55443 · PYSEC-2026-2192 · PYSEC-2026-2556
Weakness (CWE)
CWE-22 · CWE-59
Published
16 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Path traversal and symlink escape issues in langchain before 1.3.9 and langchain-anthropic before 1.4.6 let an attacker who can influence path values, search patterns, or workspace contents, including through an LLM acting on untrusted input, read files outside the intended root directory. Path-prefix checks that lack a segment boundary can also grant access to sibling paths. Upgrade langchain to 1.3.9 and langchain-anthropic to 1.4.6. Also confine filesystem-backed agent tools to a dedicated directory and do not load configuration from untrusted sources.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.1 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 11th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 12 Jun 2026, 16:56 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:11 UTC First seen by agentprime
  3. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.