← Back
CVE-2026-27795
SSRF (Server-Side Request Forgery) in @langchain/community (CVE-2026-27795)
Summary
SSRF in @langchain/community (CVE-2026-27795). Risk of unauthorized operations or information disclosure. Exploitable via ``RecursiveUrlLoader``. Mitigation: upgrade to `1.1.18` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27795** has been found in @langchain/community.
Attackers can target a specific entry point like ``RecursiveUrlLoader`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @langchain/community to **1.1.18** or later.
If unsure, ask your IT team or search "@langchain/community CVE-2026-27795" on the vendor's site.
CVE-2026-27795 (@langchain/community) — CWE-918 /
Attack vector: remote (network-reachable)
Attack surface: `RecursiveUrlLoader` / `preventOutside` / `true` / `validateSafeUrl`
Patched: `1.1.18` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in @langchain/community. Attackers reach the vulnerable code path via ``RecursiveUrlLoader`` without authentication.
📍 Affected scope
@langchain/community — . Attack surface: `RecursiveUrlLoader` / `preventOutside` / `true` / `validateSafeUrl`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.1.18**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@langchain/community' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@langchain/community' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@langchain/community` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @langchain/community to 1.1.18ステージング環境で 1.1.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@langchain/community
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.18"}]}]
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27795.json
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27795
- package https://github.com/langchain-ai/langchainjs
- web https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcommunity%401.1.14
- web https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcommunity%401.1.18
- web https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-gf3v-fwqg-4vh7
- web https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-mphv-75cg-56wg
- web https://github.com/langchain-ai/langchainjs/commit/2812d2b2b9fd9343c4850e2ab906b8cf440975ee
- web https://github.com/langchain-ai/langchainjs/commit/d5e3db0d01ab321ec70a875805b2f74aefdadf9d
- web https://github.com/langchain-ai/langchainjs/pull/9990