VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

langchain: vulnerability history, versions and safety

langchain is a package in the PyPI ecosystem. Vulert records 45 vulnerabilities for it across 120 releases, from Apr 2023 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
45 vulnerabilities recorded C12 H3 M2 L2 U26
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all langchain vulnerabilities

Vulert verdict on langchain 1.4.7 i

Updated on 23 Oct 2026

Careful: 1.4.7 has 4 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.4.7 — affected i
  • Vulnerabilities on record 45 over 3 years · 8 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 148,192 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for langchain, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.4.7 21 Oct 2026 C1 U3 MIT No Details →
1.4.6 14 Oct 2026 C1 U3 MIT No Details →
1.4.5 12 Oct 2026 C1 U3 MIT No Details →
1.4.4 08 Oct 2026 C1 U3 MIT No Details →
1.4.3 28 Sep 2026 C1 U3 MIT No Details →
1.4.2 18 Sep 2026 C1 U3 MIT No Details →
1.4.1 16 Sep 2026 C1 U3 MIT No Details →
1.4.0 03 Sep 2026 C1 U3 MIT No Details →
1.4.0a4 02 Sep 2026 C1 U3 MIT No Details →
1.4.0a3 01 Sep 2026 C1 U3 MIT No Details →
1.4.0a2 28 Aug 2026 C1 U3 MIT No Details →
1.4.0a1 27 Aug 2026 C1 U3 MIT No Details →
1.3.18 27 Aug 2026 C1 U3 MIT No Details →
1.3.17 25 Aug 2026 C1 U3 MIT No Details →
1.3.16 20 Aug 2026 C1 U3 MIT No Details →
1.3.15 11 Aug 2026 C1 U3 MIT No Details →
1.3.14 16 Jul 2026 C1 U3 MIT No Details →
1.3.13 10 Jul 2026 C1 U3 MIT No Details →
1.3.12 08 Jul 2026 C1 U3 MIT No Details →
1.3.11 22 Jun 2026 C1 U3 MIT No Details →
1.3.10 18 Jun 2026 C1 U3 MIT No Details →
1.3.9 12 Jun 2026 C1 U3 MIT No Details →
1.3.8 12 Jun 2026 M1 U1 MIT Yes Details →
1.3.7 10 Jun 2026 M1 U1 MIT Yes Details →
1.3.6 10 Jun 2026 M1 U1 MIT Yes Details →
1.3.5 10 Jun 2026 M1 U1 MIT Yes Details →
1.3.4 02 Jun 2026 M1 U1 MIT Yes Details →
1.3.3 02 Jun 2026 M1 U1 MIT Yes Details →
1.3.2 26 May 2026 M1 U1 MIT Yes Details →
1.3.1 15 May 2026 M1 U1 MIT Yes Details →
1.3.0 12 May 2026 M1 U1 MIT Yes Details →
1.2.18 08 May 2026 M1 U1 MIT Yes Details →
0.3.30 07 May 2026 M1 U1 MIT Yes Details →
1.3.0a2 06 May 2026 M1 U1 MIT Yes Details →
0.3.29 05 May 2026 M1 U2 MIT Yes Details →
1.3.0a1 01 May 2026 M1 U1 MIT Yes Details →
1.2.17 30 Apr 2026 M1 U1 MIT Yes Details →
1.2.16 29 Apr 2026 M1 U1 MIT Yes Details →
1.2.15 03 Apr 2026 M1 U1 MIT Yes Details →
1.2.14 31 Mar 2026 M1 U1 MIT Yes Details →
1.2.13 19 Mar 2026 M1 U1 MIT Yes Details →
1.2.12 11 Mar 2026 M1 U1 MIT Yes Details →
1.2.11 10 Mar 2026 M1 U1 MIT Yes Details →
0.3.28 06 Mar 2026 M1 U2 MIT Yes Details →
1.2.10 10 Feb 2026 M1 U1 MIT Yes Details →
1.2.9 06 Feb 2026 M1 U1 MIT Yes Details →
1.2.8 02 Feb 2026 M1 U1 MIT Yes Details →
1.2.7 23 Jan 2026 M1 U1 MIT Yes Details →
1.2.6 16 Jan 2026 M1 U1 MIT Yes Details →
1.2.5 16 Jan 2026 M1 U1 MIT Yes Details →
1.2.4 14 Jan 2026 M1 U1 MIT Yes Details →
1.2.3 08 Jan 2026 M1 U1 MIT Yes Details →
1.2.2 07 Jan 2026 M1 U1 MIT Yes Details →
1.2.1 07 Jan 2026 M1 U1 MIT Yes Details →
1.2.0 15 Dec 2025 M1 U1 MIT Yes Details →
1.1.3 08 Dec 2025 M1 U1 MIT Yes Details →
1.1.2 04 Dec 2025 M1 U1 MIT Yes Details →
1.1.1 04 Dec 2025 M1 U1 MIT Yes Details →
1.1.0 24 Nov 2025 M1 U1 MIT Yes Details →
1.0.8 19 Nov 2025 M1 U1 MIT Yes Details →
1.0.7 14 Nov 2025 M1 U1 MIT Yes Details →
1.0.6 14 Nov 2025 M1 U1 MIT Yes Details →
1.0.5 07 Nov 2025 M1 U1 MIT Yes Details →
1.0.4 06 Nov 2025 M1 U1 MIT Yes Details →
1.0.3 29 Oct 2025 M1 U1 MIT Yes Details →
1.0.2 21 Oct 2025 M1 U1 MIT Yes Details →
1.0.1 20 Oct 2025 M1 U1 MIT Yes Details →
1.0.0 17 Oct 2025 M1 U1 MIT Yes Details →
1.0.0rc2 17 Oct 2025 M1 U1 MIT Yes Details →
1.0.0rc1 16 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a15 15 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a14 11 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a13 10 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a12 06 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a11 06 Oct 2025 M1 U1 MIT Yes Details →
1.0.0a10 29 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a9 24 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a8 24 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a7 23 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a6 19 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a5 12 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a4 08 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a3 02 Sep 2025 M1 U1 MIT Yes Details →
1.0.0a2 28 Aug 2025 M1 U1 MIT Yes Details →
1.0.0a1 27 Aug 2025 M1 U1 MIT Yes Details →
0.4.0.dev0 05 Aug 2025 M1 U1 MIT Yes Details →
0.3.27 24 Jul 2025 M1 U2 MIT Yes Details →
0.3.26 20 Jun 2025 M1 U2 MIT Yes Details →
0.3.25 02 May 2025 M1 U3 MIT Yes Details →
0.3.24 22 Apr 2025 M1 U3 MIT Yes Details →
0.3.23 04 Apr 2025 M1 U3 MIT Yes Details →
0.3.22 31 Mar 2025 M1 U3 MIT Yes Details →
0.3.21 18 Mar 2025 M1 U3 MIT Yes Details →
0.3.20 04 Mar 2025 M1 U3 MIT Yes Details →
0.3.19 17 Feb 2025 M1 U3 MIT Yes Details →
0.3.18 07 Feb 2025 M1 U3 MIT Yes Details →
0.3.18rc2 06 Feb 2025 M1 U3 MIT Yes Details →
0.3.18rc1 03 Feb 2025 M1 U3 MIT Yes Details →
0.3.17 29 Jan 2025 M1 U3 MIT Yes Details →
0.3.16 28 Jan 2025 M1 U3 MIT Yes Details →
0.3.15 21 Jan 2025 M1 U3 — Yes Details →
0.3.14 03 Jan 2025 M1 U3 — Yes Details →
0.3.13 18 Dec 2024 M1 U3 — Yes Details →
0.3.12 14 Dec 2024 M1 U3 — Yes Details →
0.3.11 10 Dec 2024 M1 U3 — Yes Details →
0.3.10 06 Dec 2024 M1 U3 — Yes Details →
0.3.9 27 Nov 2024 M1 U3 — Yes Details →
0.3.8 23 Nov 2024 M1 U3 — Yes Details →
0.2.17 04 Nov 2024 M1 U4 — Yes Details →
0.3.7 01 Nov 2024 M1 U3 — Yes Details →
0.3.6 31 Oct 2024 M1 U3 — Yes Details →
0.3.5 30 Oct 2024 M1 U3 — Yes Details →
0.3.4 18 Oct 2024 M1 U3 — Yes Details →
0.3.3 08 Oct 2024 M1 U3 — Yes Details →
0.3.2 03 Oct 2024 M1 U3 — Yes Details →
0.3.1 25 Sep 2024 M1 U3 — Yes Details →
0.3.0 13 Sep 2024 M1 U4 — Yes Details →
0.3.0.dev2 11 Sep 2024 M1 U4 — Yes Details →
0.3.0.dev1 05 Sep 2024 M1 U4 — Yes Details →
0.2.16 03 Sep 2024 M1 U4 — Yes Details →

The newest 120 of 524 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 28
  • 2024 9
  • 2026 8

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 8 of the 45 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for langchain

The 5 most severe of 45 vulnerabilities recorded for this package

Search all 45 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-29374: LangChain Code Injection Vulnerability 9.8 critical No fix published 05 Apr 2023
CVE-2023-36095: langchain Code Injection vulnerability 9.8 critical 0.0.236 05 Aug 2023
CVE-2023-34540: Langchain OS Command Injection vulnerability 9.8 critical 0.0.225 14 Jun 2023
CVE-2023-32785: Langchain SQL Injection Vulnerability 9.8 critical 0.0.247 29 Jun 2026
Langchain SQL Injection Vulnerability in langchain 9.8 critical 0.0.247 21 Oct 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About langchain

Is langchain safe to use?

Vulert records 45 vulnerabilities for langchain in PyPI: 12 critical, 3 high, 2 medium and 2 low, plus 26 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is langchain's Vulert package health score?

Vulert scores langchain 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of langchain affected?

Yes. 1.4.7, the version you would install today, has 4 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does langchain have?

45 vulnerabilities are recorded for langchain in the PyPI ecosystem: 12 critical, 3 high, 2 medium and 2 low, plus 26 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new langchain vulnerabilities disclosed?

8 vulnerabilities were recorded for langchain in the last 12 months, and the oldest entry in this database dates to 05 Apr 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of langchain are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor langchain for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the langchain version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.