Quick answers
- Is CVE-2026-55615 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55615 being exploited in the wild.
- How severe is CVE-2026-55615?
- Critical severity, with a CVSS score of 4, published 10 July 2026.
- Which products and versions are affected?
- langroid (PyPI) <= 0.65.4, ECOSYSTEM:introduced=0,fixed=0.65.5.
- Is there a fix for CVE-2026-55615?
- Yes. langroid (PyPI): upgrade to 0.65.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55615 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55615?
- Check whether you run langroid (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langroid (PyPI): upgrade to 0.65.5 or later
pip install "langroid>=0.65.5"
Technical details
The Neo4jChatAgent and ArangoChatAgent components in Langroid pass LLM-generated Cypher and AQL queries directly to their respective database drivers without validation, statement-type allowlists, or opt-out gates. Because the query text is influenceable via prompt injection (either through direct user input or indirect RAG content), an attacker can execute arbitrary database commands. This allows for unauthorized data retrieval and destruction. Furthermore, if the database environment has extended procedures enabled (such as Neo4j's APOC/dbms.security or ArangoDB's UDFs/Foxx), an attacker can achieve filesystem access and remote code execution (RCE). This issue is an incomplete fix of the class of vulnerability addressed in CVE-2026-25879. The vulnerability is resolved in version 0.65.5 by introducing a validation layer and an 'allow_dangerous_operations' configuration gate.
Affected products
- langroid langroid < 0.65.5
Identifiers
- CVE-2026-55615
- GHSA-2pq5-3q89-j7cc
- PYSEC-2026-2576
Timeline
- 2026-06-14: patched: Fix committed to repository
- 2026-06-15: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: CVE published to NVD