Live › vulnerability › CVE-2026-114510
Go to dashboardFlexible GraphRAG versions 0.6.0 through 0.8.2 escape quotes in the wrong order in the FalkorDB adapter, so entity values produced by the extraction model from ingested documents can break out of Cypher strings. An attacker who controls document content can modify or delete graph data and, where query results reach the user or LLM, read graph data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Flexible GraphRAG with the langchain graph backend and FalkorDB as the graph database are exposed, especially if ingested documents come from users or external sources the team does not control. The LlamaIndex FalkorDB store is not affected, and deployments on other graph databases or versions outside 0.6.0 to 0.8.2 can skip it.
No product ranges from the sources yet.
pip show flexible-graphrag, and whether it falls between 0.6.0 and 0.8.2.GRAPH_BACKEND=langchain and GRAPH_DB=falkordb.0.8.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Flexible GraphRAG is a Python framework for building graph and retrieval-augmented generation applications across multiple graph, vector, and search backends. From 0.6.0 until 0.8.2, the _escape() helper in flexible-graphrag/langchain/graph/pg_store_adapters/falkordb_adapter.py escapes quotes before backslashes and then interpolates the result into Cypher assembled by FalkorDBAdapter.add_graph_documents, allowing an inserted escape to be doubled and a quote to terminate the string early. When GRAPH_BACKEND=langchain and GRAPH_DB=falkordb are configured, attacker-influenced ingested document content can cause the extraction model to produce malicious entity or relationship values that reach these queries, allowing injected Cypher clauses to modify or delete graph data and, when the calling code surfaces query results to the user or LLM, disclose graph data. Dynamic node and relationship type identifiers are also inserted into backtick-quoted query positions without safe parameterization. The LlamaIndex FalkorDB store is not affected. This issue is fixed in version 0.8.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-114510")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.