Widely-used integration framework with Neo4j support; could disrupt orgs using Camel-Neo4j by data access compromise.
CVE-2026-46591
Cypher injection via untrusted JSON keys in Camel Neo4j component.
Is CVE-2026-46591 being exploited?
Not confirmed. CVE-2026-46591 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-46591?
CVE-2026-46591 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46591?
Yes. A fix has been recorded for CVE-2026-46591. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46591 affect?
CVE-2026-46591 affects Apache Camel Neo4j component (versions 4.10.0–4.21.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46591?
Upgrade to 4.21.0; validate/allow-list property names; filter inbound Camel headers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker controls property names in CamelNeo4jMatchProperties; injects Cypher to read/modify/delete Neo4j data.
Patch when possible
- affected>= 4.10.0 and < 4.14.8
- affected>= 4.15.0 and < 4.18.3
- affected>= 4.19.0 and < 4.21.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.