VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

langchain-core: vulnerability history, versions and safety

langchain-core is a package in the PyPI ecosystem. Vulert records 18 vulnerabilities for it across 85 releases, from Mar 2024 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
18 vulnerabilities recorded C1 H3 M3 L1 U10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
15 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-core vulnerabilities

Vulert verdict on langchain-core 1.7.0 i

Updated on 23 Oct 2026

Good news: 1.7.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 18.

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

What to do: Stay on 1.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.7.0 — unaffected i
  • Vulnerabilities on record 18 over 2 years · 15 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 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-core, 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.7.0 22 Oct 2026 none MIT — Details →
1.6.13 21 Oct 2026 none MIT — Details →
1.6.12 16 Oct 2026 none MIT — Details →
1.6.11 15 Oct 2026 none MIT — Details →
1.6.10 12 Oct 2026 none MIT — Details →
1.6.9 08 Oct 2026 none MIT — Details →
1.6.8 08 Oct 2026 none MIT — Details →
1.6.7 06 Oct 2026 none MIT — Details →
1.6.6 29 Sep 2026 none MIT — Details →
1.6.5 24 Sep 2026 none MIT — Details →
1.6.4 21 Sep 2026 none MIT — Details →
1.6.3 11 Sep 2026 none MIT — Details →
1.6.2 04 Sep 2026 none MIT — Details →
1.6.1 27 Aug 2026 none MIT — Details →
1.6.0 19 Aug 2026 none MIT — Details →
1.5.6 17 Aug 2026 none MIT — Details →
1.5.5 14 Aug 2026 none MIT — Details →
1.5.4 11 Aug 2026 none MIT — Details →
1.5.3 30 Jul 2026 none MIT — Details →
1.5.2 28 Jul 2026 none MIT — Details →
1.5.1 23 Jul 2026 none MIT — Details →
1.5.0 21 Jul 2026 none MIT — Details →
1.4.9 08 Jul 2026 none MIT — Details →
1.4.8 18 Jun 2026 none MIT — Details →
1.4.7 12 Jun 2026 none MIT — Details →
1.4.6 11 Jun 2026 none MIT — Details →
1.4.5 11 Jun 2026 none MIT — Details →
1.4.4 10 Jun 2026 none MIT — Details →
1.4.3 09 Jun 2026 none MIT — Details →
1.4.2 08 Jun 2026 none MIT — Details →
1.4.1 05 Jun 2026 none MIT — Details →
1.4.0 11 May 2026 none MIT — Details →
0.3.86 07 May 2026 U2 MIT Yes Details →
0.3.85 05 May 2026 U2 MIT Yes Details →
1.3.3 05 May 2026 none MIT — Details →
1.4.0a2 01 May 2026 none MIT — Details →
1.4.0a1 01 May 2026 none MIT — Details →
1.3.2 24 Apr 2026 H1 U1 MIT Yes Details →
1.3.1 23 Apr 2026 H1 U1 MIT Yes Details →
1.3.0 17 Apr 2026 H1 U1 MIT Yes Details →
1.3.0a3 16 Apr 2026 H1 U1 MIT Yes Details →
1.2.31 16 Apr 2026 H1 U1 MIT Yes Details →
1.2.30 15 Apr 2026 H1 U1 MIT Yes Details →
1.2.29 14 Apr 2026 H1 U1 MIT Yes Details →
1.3.0a2 13 Apr 2026 H1 U1 MIT Yes Details →
1.3.0a1 10 Apr 2026 H1 U1 MIT Yes Details →
0.3.84 08 Apr 2026 U4 MIT Yes Details →
1.2.28 08 Apr 2026 H1 U1 MIT Yes Details →
1.2.27 07 Apr 2026 H1 U2 MIT Yes Details →
1.2.26 03 Apr 2026 H1 U2 MIT Yes Details →
1.2.25 02 Apr 2026 H1 U2 MIT Yes Details →
1.2.24 01 Apr 2026 H1 U2 MIT Yes Details →
1.2.23 27 Mar 2026 H1 U2 MIT Yes Details →
1.2.22 24 Mar 2026 H1 U2 MIT Yes Details →
1.2.21 23 Mar 2026 H2 U4 MIT Yes Details →
1.2.20 18 Mar 2026 H2 U4 MIT Yes Details →
1.2.19 13 Mar 2026 H2 U4 MIT Yes Details →
1.2.18 09 Mar 2026 H2 U4 MIT Yes Details →
1.2.17 02 Mar 2026 H2 U4 MIT Yes Details →
1.2.16 25 Feb 2026 H2 U4 MIT Yes Details →
1.2.15 23 Feb 2026 H2 U4 MIT Yes Details →
1.2.14 19 Feb 2026 H2 U4 MIT Yes Details →
1.2.13 15 Feb 2026 H2 U4 MIT Yes Details →
1.2.12 12 Feb 2026 H2 U4 MIT Yes Details →
1.2.11 10 Feb 2026 H2 U4 MIT Yes Details →
1.2.10 10 Feb 2026 H2 L1 U5 MIT Yes Details →
1.2.9 05 Feb 2026 H2 L1 U5 MIT Yes Details →
1.2.8 02 Feb 2026 H2 L1 U5 MIT Yes Details →
0.3.83 13 Jan 2026 H1 M1 L1 U5 MIT Yes Details →
0.3.82 09 Jan 2026 H1 M1 L1 U5 MIT Yes Details →
1.2.7 09 Jan 2026 H2 L1 U5 MIT Yes Details →
1.2.6 02 Jan 2026 H2 L1 U5 MIT Yes Details →
0.3.81 23 Dec 2025 H1 M1 L1 U5 MIT Yes Details →
1.2.5 22 Dec 2025 H2 L1 U5 MIT Yes Details →
1.2.4 19 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.2.3 18 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.2.2 16 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.2.1 15 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.2.0 12 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.1.3 09 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.1.2 08 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.1.1 04 Dec 2025 C1 H2 L1 U5 MIT Yes Details →
1.1.0 21 Nov 2025 C1 H2 L1 U5 MIT Yes Details →
0.3.80 19 Nov 2025 H1 M1 L1 U6 MIT Yes Details →
1.0.7 19 Nov 2025 C1 H2 L1 U5 MIT Yes Details →
1.0.6 19 Nov 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.5 14 Nov 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.4 07 Nov 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.3 03 Nov 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.2 29 Oct 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.1 24 Oct 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.0 17 Oct 2025 C1 H3 L1 U6 MIT Yes Details →
1.0.0rc3 17 Oct 2025 H1 L1 U4 MIT Yes Details →
1.0.0rc2 16 Oct 2025 H1 L1 U4 MIT Yes Details →
1.0.0rc1 15 Oct 2025 H1 L1 U4 MIT Yes Details →
0.3.79 09 Oct 2025 H1 M1 L1 U7 MIT Yes Details →
1.0.0a8 07 Oct 2025 H1 L1 U4 MIT Yes Details →
1.0.0a7 06 Oct 2025 H1 L1 U4 MIT Yes Details →
0.3.78 03 Oct 2025 H1 M1 L1 U7 MIT Yes Details →
1.0.0a6 02 Oct 2025 H1 L1 U4 MIT Yes Details →
0.3.77 01 Oct 2025 H1 M1 L1 U7 — Yes Details →
1.0.0a5 30 Sep 2025 H1 L1 U4 — Yes Details →
1.0.0a4 18 Sep 2025 H1 L1 U4 — Yes Details →
1.0.0a3 18 Sep 2025 H1 L1 U4 — Yes Details →
0.3.76 10 Sep 2025 H1 M1 L1 U7 — Yes Details →
1.0.0a2 02 Sep 2025 H1 L1 U4 — Yes Details →
1.0.0a1 27 Aug 2025 H1 L1 U4 — Yes Details →
0.3.75 26 Aug 2025 H1 M1 L1 U7 — Yes Details →
0.3.74 07 Aug 2025 H1 M1 L1 U7 — Yes Details →
0.3.73 07 Aug 2025 H1 M1 L1 U7 — Yes Details →
0.4.0.dev0 05 Aug 2025 H1 L1 U3 — Yes Details →
0.3.72 24 Jul 2025 H1 M1 L1 U7 — Yes Details →
0.3.71 22 Jul 2025 H1 M1 L1 U7 — Yes Details →
0.3.70 21 Jul 2025 H1 M1 L1 U7 — Yes Details →
0.3.69 15 Jul 2025 H1 M1 L1 U7 — Yes Details →
0.3.68 03 Jul 2025 H1 M1 L1 U7 — Yes Details →
0.3.67 30 Jun 2025 H1 M1 L1 U7 — Yes Details →
0.3.66 20 Jun 2025 H1 M1 L1 U7 — Yes Details →
0.3.65 10 Jun 2025 H1 M1 L1 U7 — Yes Details →
0.3.64 05 Jun 2025 H1 M1 L1 U7 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 3
  • 2026 13

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

03 Vulnerabilities

Recorded vulnerabilities for langchain-core

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-68664: LangChain Serialization Injection Vulnerability Allows Secret Extraction 9.3 critical 1.2.5 23 Dec 2025
CVE-2025-68664: LangChain Serialization Injection Vulnerability Enables Secret Extraction 9.3 critical 0.3.81 29 Jun 2026
CVE-2025-65106: LangChain Template Injection Vulnerability in Prompt Templates 8.3 high 0.3.80 07 Jul 2026
CVE-2025-65106: LangChain Template Injection Vulnerability in Prompt Templates 8.3 high 1.0.7 20 Nov 2025
CVE-2026-44843: LangChain Unsafe Deserialization Vulnerability 8.2 high 0.3.85 13 Jul 2026

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-core

Is langchain-core safe to use?

Vulert records 18 vulnerabilities for langchain-core in PyPI: 1 critical, 3 high, 3 medium and 1 low, plus 10 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is langchain-core's Vulert package health score?

Vulert scores langchain-core 69/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).

Is the latest version of langchain-core affected?

No. 1.7.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does langchain-core have?

18 vulnerabilities are recorded for langchain-core in the PyPI ecosystem: 1 critical, 3 high, 3 medium and 1 low, plus 10 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-core vulnerabilities disclosed?

15 vulnerabilities were recorded for langchain-core in the last 12 months, and the oldest entry in this database dates to 04 Mar 2024. 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-core 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-core for upcoming vulnerabilities?

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