CVE-2026-55615 is an injection vulnerability in Langroid's Neo4jChatAgent affecting versions prior to 0.65.5. The component forwards LLM-generated Cypher statements directly to the Neo4j driver without validation, without a statement-type allowlist, and without a protective opt-in gate for dangerous operations. Because the generated Cypher can be influenced by prompt injection through direct user input or indirectly through retrieval-augmented content consumed by the agent, an attacker can steer the model into producing attacker-controlled database queries. Successful exploitation enables unauthorized execution of arbitrary Cypher within the privileges available to the configured Neo4j connection. This can expose, modify, or delete graph data, and in deployments where Neo4j dangerous procedures are enabled, can extend beyond the database boundary to operating-system command execution and filesystem interaction.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.