Is langchain-classic 1.0 vulnerable?

PyPI · 9 releases from 1.0.0 to 1.0.8 · latest langchain-classic is 1.0.8 · checked 20 Nov 2026

No known advisories in the last release

langchain-classic 1.0.8, the last 1.0 release, has no known advisories. 1 advisory affects earlier 1.0.x releases, so update to 1.0.8.

Update within 1.0:pip install 'langchain-classic>=1.0.8'

Is your project on an affected langchain-classic?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.0.x, affecting earlier releases

  • HighCVE-2026-45134GHSA-3644-q5cj-c5c713 May 2026

    LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning

    Affected
    <1.0.7
    Fixed in
    1.0.7

Every langchain-classic 1.0.x release

Affected: 1.0.0 to 1.0.6. 1.0.7 and later are not affected.

VersionKnown advisories
langchain-classic 1.0.8None
langchain-classic 1.0.7None
langchain-classic 1.0.6CVE-2026-45134
langchain-classic 1.0.5CVE-2026-45134
langchain-classic 1.0.4CVE-2026-45134
langchain-classic 1.0.3CVE-2026-45134
langchain-classic 1.0.2CVE-2026-45134
langchain-classic 1.0.1CVE-2026-45134
langchain-classic 1.0.0CVE-2026-45134

Which of your client projects are still on langchain-classic 1.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact langchain-classic version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.