LangChain vulnerabilities and security advisories
The newest reviewed advisories for langchain, @langchain/core, @langchain/community and @langchain/openai on npm. Each one shows which versions are affected, which version fixes it, and a prompt that has your AI agent check your project and upgrade only if it needs to.
Get an email when LangChain has a new one
Email alerts are coming soon. This page updates every hour.
$ latest 5 · 1 critical, high or exploited
- mediumFeb 25, 2026
LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader
- @langchain/community <= 1.1.17 · fixed in 1.1.18
GHSA-mphv-75cg-56wgCVE-2026-27795prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-mphv-75cg-56wg (CVE-2026-27795), severity medium What it is: LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader Affected packages: - @langchain/community: affected versions <= 1.1.17. Fixed in 1.1.18. Details: https://github.com/advisories/GHSA-mphv-75cg-56wg Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumFeb 11, 2026
@langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation
- @langchain/community <= 1.1.13 · fixed in 1.1.14
GHSA-gf3v-fwqg-4vh7CVE-2026-26019prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-gf3v-fwqg-4vh7 (CVE-2026-26019), severity medium What it is: @langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation Affected packages: - @langchain/community: affected versions <= 1.1.13. Fixed in 1.1.14. Details: https://github.com/advisories/GHSA-gf3v-fwqg-4vh7 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highDec 23, 2025
LangChain serialization injection vulnerability enables secret extraction
- @langchain/core >= 1.0.0, < 1.1.8 · fixed in 1.1.8
- @langchain/core < 0.3.80 · fixed in 0.3.80
- langchain >= 1.0.0, < 1.2.3 · fixed in 1.2.3
- langchain < 0.3.37 · fixed in 0.3.37
GHSA-r399-636x-v7f6CVE-2025-68665prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-r399-636x-v7f6 (CVE-2025-68665), severity high What it is: LangChain serialization injection vulnerability enables secret extraction Affected packages: - @langchain/core: affected versions >= 1.0.0, < 1.1.8. Fixed in 1.1.8. - @langchain/core: affected versions < 0.3.80. Fixed in 0.3.80. - langchain: affected versions >= 1.0.0, < 1.2.3. Fixed in 1.2.3. - langchain: affected versions < 0.3.37. Fixed in 0.3.37. Details: https://github.com/advisories/GHSA-r399-636x-v7f6 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - lowOct 29, 2024
@langchain/community SQL Injection vulnerability
- @langchain/community < 0.3.3 · fixed in 0.3.3
GHSA-6m59-8fmv-m5f9CVE-2024-7042prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-6m59-8fmv-m5f9 (CVE-2024-7042), severity low What it is: @langchain/community SQL Injection vulnerability Affected packages: - @langchain/community: affected versions < 0.3.3. Fixed in 0.3.3. Details: https://github.com/advisories/GHSA-6m59-8fmv-m5f9 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 29, 2024
Langchain Path Traversal vulnerability
- langchain < 0.2.19 · fixed in 0.2.19
GHSA-hc5w-c9f8-9cc4CVE-2024-7774prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-hc5w-c9f8-9cc4 (CVE-2024-7774), severity medium What it is: Langchain Path Traversal vulnerability Affected packages: - langchain: affected versions < 0.2.19. Fixed in 0.2.19. Details: https://github.com/advisories/GHSA-hc5w-c9f8-9cc4 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now.
From the GitHub Advisory Database, refreshed hourly. Full history on GitHub.
Keeping LangChain patched
npm audit(orpnpm audit) lists known vulnerable packages in your lockfile, including ones pulled in by other packages.- Turn on Dependabot for your GitHub repo and it opens the upgrade for you when an advisory lands.
- A patched framework doesn't cover your own setup: headers, cookies and HTTPS. The free check looks at those.