CVE-2026-114510 stevereiner CVE debrief

Who should care

Defenders and developers using Flexible GraphRAG, especially those with GRAPH_BACKEND=langchain and GRAPH_DB=falkordb configured, should assess exposure and prioritize patching to prevent potential graph data modifications or disclosures.

Why it matters

CVE-2026-114510 is a high-severity vulnerability in Flexible GraphRAG that allows Cypher injection attacks, potentially leading to graph data modifications, deletions, or disclosures. Defenders should prioritize patching to version 0.8.2 or later, assess exposure in their environments, and monitor for suspicious activity. The vulnerability requires verification from official sources for affected versions, exploitation, and remediation.

• Potential graph data modifications or deletions
• Possible disclosure of sensitive graph data
• Need for patching to prevent exploitation
• Verification of environment exposure and inventory checks

Technical summary

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. This allows an inserted escape to be doubled and a quote to terminate the string early, enabling Cypher injection attacks. The vulnerability affects Flexible GraphRAG versions between 0.6.0 and 0.8.2. The LlamaIndex FalkorDB store is not affected. Dynamic node and relationship type identifiers are also inserted into backtick-quoted query positions without safe parameterization.

Defensive priority

Defenders should prioritize patching to version 0.8.2 or later, assess exposure in their environments, and monitor for suspicious activity.

Recommended defensive actions

• Patch Flexible GraphRAG to version 0.8.2 or later
• Assess exposure in environments using Flexible GraphRAG
• Monitor for suspicious activity related to graph data modifications or disclosures
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed version. However, the corpus does not establish versions, exploitation, impact, or remediation beyond patching.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.