VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@langchain/community: vulnerability history, versions and safety

@langchain/community is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 99 releases, from Oct 2024 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 25 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @langchain/community vulnerabilities

Vulert verdict on @langchain/community 1.1.29 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Inactive

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 1.1.29 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 2 in the last year i
  • Latest disclosure 25 Feb 2026 i
  • Highest CVSS 4.9 i
  • With no published fix 0 i
  • Depended on by 132 packages i
  • Stars 9 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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/community, 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.1.29 27 May 2026 none MIT — Details →
1.1.28 04 May 2026 none MIT — Details →
1.1.27 31 Mar 2026 none MIT — Details →
1.1.26 30 Mar 2026 none MIT — Details →
1.1.25 24 Mar 2026 none MIT — Details →
1.2.0-dev-1773962633795 19 Mar 2026 none MIT — Details →
1.2.0-dev-1773786580575 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773785150055 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773776071697 17 Mar 2026 none MIT — Details →
1.1.24 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773712098100 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773710628974 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773709997654 17 Mar 2026 none MIT — Details →
1.2.0-dev-1773698445534 16 Mar 2026 none MIT — Details →
1.2.0-dev-1773345797648 12 Mar 2026 none MIT — Details →
1.1.23 11 Mar 2026 none MIT — Details →
1.1.22 03 Mar 2026 none MIT — Details →
1.1.21 02 Mar 2026 none MIT — Details →
1.1.20 26 Feb 2026 none MIT — Details →
1.1.19 24 Feb 2026 none MIT — Details →
1.1.18 23 Feb 2026 none MIT — Details →
1.1.17 20 Feb 2026 M1 MIT Yes Details →
1.1.16 17 Feb 2026 M1 MIT Yes Details →
1.1.16-dev-1771365493298 17 Feb 2026 M1 MIT Yes Details →
1.1.15 12 Feb 2026 M1 MIT Yes Details →
1.1.14 11 Feb 2026 M1 MIT Yes Details →
1.1.13 09 Feb 2026 M2 MIT Yes Details →
1.1.12 05 Feb 2026 M2 MIT Yes Details →
1.1.11 04 Feb 2026 M2 MIT Yes Details →
1.1.10 30 Jan 2026 M2 MIT Yes Details →
1.1.9 28 Jan 2026 M2 MIT Yes Details →
1.1.8 26 Jan 2026 M2 MIT Yes Details →
1.1.7 24 Jan 2026 M2 MIT Yes Details →
1.1.6 22 Jan 2026 M2 MIT Yes Details →
1.1.5 20 Jan 2026 M2 MIT Yes Details →
1.1.5-dev-1768440391024 15 Jan 2026 M2 MIT Yes Details →
1.1.4 13 Jan 2026 M2 MIT Yes Details →
1.1.3 08 Jan 2026 M2 MIT Yes Details →
1.1.2 06 Jan 2026 M2 MIT Yes Details →
0.3.59 23 Dec 2025 M2 MIT Yes Details →
1.1.1 18 Dec 2025 M2 MIT Yes Details →
1.1.1-dev-1765937705265 17 Dec 2025 M2 MIT Yes Details →
1.1.0 13 Dec 2025 M2 MIT Yes Details →
1.1.0-dev-1765433794876 11 Dec 2025 M2 MIT Yes Details →
1.1.0-dev-1765432861398 11 Dec 2025 M2 MIT Yes Details →
1.1.0-dev-1765431816670 11 Dec 2025 M2 MIT Yes Details →
1.0.7 05 Dec 2025 M2 MIT Yes Details →
1.0.6 02 Dec 2025 M2 MIT Yes Details →
1.0.5 24 Nov 2025 M2 MIT Yes Details →
1.0.4 18 Nov 2025 M2 MIT Yes Details →
0.3.58 17 Nov 2025 M2 MIT Yes Details →
1.0.3 14 Nov 2025 M2 MIT Yes Details →
1.0.2 11 Nov 2025 M2 MIT Yes Details →
1.0.0 18 Oct 2025 M2 MIT Yes Details →
1.0.0-alpha.1 14 Oct 2025 M2 MIT Yes Details →
0.3.57 29 Sep 2025 M2 MIT Yes Details →
0.3.56 15 Sep 2025 M2 MIT Yes Details →
0.3.55 05 Sep 2025 M2 MIT Yes Details →
0.3.54 02 Sep 2025 M2 MIT Yes Details →
0.3.53 18 Aug 2025 M2 MIT Yes Details →
0.3.52 18 Aug 2025 M2 MIT Yes Details →
0.3.51 15 Aug 2025 M2 MIT Yes Details →
0.3.50 07 Aug 2025 M2 MIT Yes Details →
0.3.49 15 Jul 2025 M2 MIT Yes Details →
0.3.48 03 Jul 2025 M2 MIT Yes Details →
0.3.47 20 Jun 2025 M2 MIT Yes Details →
0.3.46 11 Jun 2025 M2 MIT Yes Details →
0.3.45 28 May 2025 M2 MIT Yes Details →
0.3.44 22 May 2025 M2 MIT Yes Details →
0.3.43 16 May 2025 M2 MIT Yes Details →
0.3.42 30 Apr 2025 M2 MIT Yes Details →
0.3.41 17 Apr 2025 M2 MIT Yes Details →
0.3.40 09 Apr 2025 M2 MIT Yes Details →
0.3.39 02 Apr 2025 M2 MIT Yes Details →
0.3.38 30 Mar 2025 M2 MIT Yes Details →
0.3.37 24 Mar 2025 M2 MIT Yes Details →
0.3.36 17 Mar 2025 M2 MIT Yes Details →
0.3.35 13 Mar 2025 M2 MIT Yes Details →
0.3.34 04 Mar 2025 M2 MIT Yes Details →
0.3.33 27 Feb 2025 M2 MIT Yes Details →
0.3.32 21 Feb 2025 M2 MIT Yes Details →
0.3.31 18 Feb 2025 M2 MIT Yes Details →
0.3.30 11 Feb 2025 M2 MIT Yes Details →
0.3.29 06 Feb 2025 M2 MIT Yes Details →
0.3.28 30 Jan 2025 M2 MIT Yes Details →
0.3.27 25 Jan 2025 M2 MIT Yes Details →
0.3.26 20 Jan 2025 M2 MIT Yes Details →
0.3.25 18 Jan 2025 M2 MIT Yes Details →
0.3.24 10 Jan 2025 M2 MIT Yes Details →
0.3.23 09 Jan 2025 M2 MIT Yes Details →
0.3.22 02 Jan 2025 M2 MIT Yes Details →
0.3.21 31 Dec 2024 M2 MIT Yes Details →
0.3.20 24 Dec 2024 M2 MIT Yes Details →
0.3.19 14 Dec 2024 M2 MIT Yes Details →
0.3.18 11 Dec 2024 M2 MIT Yes Details →
0.3.17 04 Dec 2024 M2 MIT Yes Details →
0.3.16 25 Nov 2024 M2 MIT Yes Details →
0.3.15 17 Nov 2024 M2 MIT Yes Details →
0.3.14 13 Nov 2024 M2 MIT Yes Details →
0.3.13 12 Nov 2024 M2 MIT Yes Details →
0.3.12 05 Nov 2024 M2 — Yes Details →
0.3.11 29 Oct 2024 M2 — Yes Details →
0.3.10 26 Oct 2024 M2 — Yes Details →
0.3.9 25 Oct 2024 M2 — Yes Details →
0.3.8 23 Oct 2024 M2 — Yes Details →
0.3.7 20 Oct 2024 M2 — Yes Details →
0.3.7-rc.0 20 Oct 2024 M2 — Yes Details →
0.3.6 17 Oct 2024 M2 — Yes Details →
0.3.5 11 Oct 2024 M2 — Yes Details →
0.3.4 30 Sep 2024 M2 — Yes Details →
0.3.3 25 Sep 2024 M2 — Yes Details →
0.3.2 23 Sep 2024 M2 L1 — Yes Details →
0.3.2-rc.1 23 Sep 2024 M2 L1 — Yes Details →
0.3.2-rc.0 22 Sep 2024 M2 L1 — Yes Details →
0.3.1 17 Sep 2024 M2 L1 — Yes Details →
0.3.0 14 Sep 2024 M2 L1 — Yes Details →
0.2.33 10 Sep 2024 M2 L1 — Yes Details →
0.3.0-rc.0 07 Sep 2024 M2 L1 — Yes Details →
0.2.32 04 Sep 2024 M2 L1 — Yes Details →
0.2.31 23 Aug 2024 M2 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for @langchain/community

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-7042: SQL Injection Vulnerability in @langchain/community Package 4.9 low 0.3.3 29 Oct 2024
SSRF Bypass Vulnerability in @langchain/community's RecursiveUrlLoader 4.1 medium 1.1.14 11 Feb 2026
CVE-2026-27795: SSRF Bypass in @langchain/community's RecursiveUrlLoader 4.1 medium 1.1.18 25 Feb 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/community

Is @langchain/community safe to use?

Vulert records 3 vulnerabilities for @langchain/community in npm: 0 critical, 0 high, 2 medium and 1 low. 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/community's Vulert package health score?

Vulert scores @langchain/community 45/100, which reads as risky. 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of @langchain/community affected?

No. 1.1.29, 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.

Which version of @langchain/community should I use?

1.1.29 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @langchain/community have?

3 vulnerabilities are recorded for @langchain/community in the npm ecosystem: 0 critical, 0 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @langchain/community vulnerabilities disclosed?

2 vulnerabilities were recorded for @langchain/community in the last 12 months, and the oldest entry in this database dates to 29 Oct 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/community 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/community for upcoming vulnerabilities?

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