Is langchain-community 0.2 vulnerable?
PyPI · 19 releases from 0.2.0 to 0.2.19 · latest langchain-community is 0.4.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. langchain-community 0.2.19, the last 0.2 release, is affected by 1 known security advisory (1 high), including CVE-2025-6984. 4 more affect earlier 0.2.x releases. Upgrade to 0.3.27 or later to fix all of them.
pip install 'langchain-community>=0.3.27'Is your project on an affected langchain-community?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting langchain-community 0.2.19
Langchain Community Vulnerable to XML External Entity (XXE) Attacks
- Affected
- <0.3.27
- Fixed in
- 0.3.27
Fixed within 0.2.x, affecting earlier releases
Langchain SQL Injection vulnerability
- Affected
- >=0.2.0 <0.2.19
- Fixed in
- 0.2.19
LangChain pickle deserialization of untrusted data
- Affected
- <0.2.4
- Fixed in
- 0.2.4
Denial of service in langchain-community
- Affected
- <0.2.5
- Fixed in
- 0.2.5
Server-Side Request Forgery in langchain-community.retrievers.web_research.WebResearchRetriever
- Affected
- <0.2.9
- Fixed in
- 0.2.9
Every langchain-community 0.2.x release
Affected: 0.2.0 to 0.2.19. Latest langchain-community: 0.4.2.
| Version | Known advisories |
|---|---|
| langchain-community 0.2.19 | CVE-2025-6984 |
| langchain-community 0.2.18 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.17 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.16 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.15 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.14 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.13 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.12 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.11 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.10 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.9 | CVE-2025-6984, CVE-2024-8309 |
| langchain-community 0.2.7 | CVE-2025-6984, CVE-2024-8309, CVE-2024-3095 |
| langchain-community 0.2.6 | CVE-2025-6984, CVE-2024-8309, CVE-2024-3095 |
| langchain-community 0.2.5 | CVE-2025-6984, CVE-2024-8309, CVE-2024-3095 |
| langchain-community 0.2.4 | CVE-2025-6984, CVE-2024-8309, CVE-2024-2965, CVE-2024-3095 |
| langchain-community 0.2.3 | CVE-2025-6984, CVE-2024-8309, CVE-2024-5998, CVE-2024-2965, CVE-2024-3095 |
| langchain-community 0.2.2 | CVE-2025-6984, CVE-2024-8309, CVE-2024-5998, CVE-2024-2965, CVE-2024-3095 |
| langchain-community 0.2.1 | CVE-2025-6984, CVE-2024-8309, CVE-2024-5998, CVE-2024-2965, CVE-2024-3095 |
| langchain-community 0.2.0 | CVE-2025-6984, CVE-2024-8309, CVE-2024-5998, CVE-2024-2965, CVE-2024-3095 |
Which of your client projects are still on langchain-community 0.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact langchain-community version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other langchain-community versions
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.