Vulnerability in langroid (CVE-2026-55615)
Summary
Vulnerability in langroid (CVE-2026-55615). Risk of unauthorized operations or information disclosure. Exploitable via Neo4jChatAgent. Mitigation: upgrade to 0.65.5 or later.
Original description
The description as published by the source.
Langroid is a framework for building large-language-model-powered applications. Prior to version 0.65.5, Neo4jChatAgent passes LLM-generated Cypher queries straight to the Neo4j driver with no validation, no statement-type allowlist, and no opt-out gate. The query text is influenceable by prompt injection (direct user input or indirect content the agent reads back via RAG), so an attacker who can influence the prompt can read or destroy all graph data and, when APOC or dbms.security procedures are enabled on the server, achieve OS-command and filesystem access. This is the same defect class and threat model as the SQLChatAgent prompt-to-SQL-to-RCE issue fixed in version 0.63.0 (CVE-2026-25879); that fix did not extend to the neo4j module. Version 0.65.5 contains a fix for the neo4j module.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55615 has been found in langroid.
Attackers can target a specific entry point like Neo4jChatAgent over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade langroid to 0.65.5 or later.
If unsure, ask your IT team or search "langroid CVE-2026-55615" on the vendor's site.
CVE-2026-55615 (langroid) — CWE-74
Attack surface: Neo4jChatAgent / ArangoChatAgent / allow_dangerous_operations / False
Patched: 0.65.5 — 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.
A vulnerability (CWE-74) exists in langroid. Attackers reach the vulnerable code path via Neo4jChatAgent.
Check the vendor advisory for the affected versions of langroid. Attack surface: Neo4jChatAgent / ArangoChatAgent / allow_dangerous_operations / False.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.65.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'langroid' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'langroid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
langroidを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade langroid to 0.65.5ステージング環境で 0.65.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com