Apache Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation, allowing Cypher injection (incomplete remediation…

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

EPSS

• CVE-2026-46591: 0.55% estimated exploitation activity in the next 30 days; percentile 46.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Improper Neutralization of Special Elements in Data Query Logic vulnerability in Apache Camel Neo4j component. The camel-neo4j producer builds the Cypher WHERE clause for its match/retrieve and delete operations from the CamelNeo4jMatchProperties map. CVE-2025-66169 addressed Cypher injection through the property values by binding them as query parameters ($paramN), but the property names (the JSON keys of that map) were still concatenated into the query string verbatim in Neo4jProducer.retrieveNodes() and deleteNode(). A property name containing Cypher syntax therefore alters the structure of the executed query. Where a route maps untrusted input into the CamelNeo4jMatchProperties map - for example by passing a request body as the match map, or from a consumer that does not filter inbound Camel headers - an attacker who controls the JSON key names can inject arbitrary Cypher and read, modify or delete any node or relationship in the Neo4j database. The CamelNeo4jMatchProperties…

Published by the source

6 Jul 2026, 09:30 UTC

Last modified by the source

28 Aug 2026, 19:31 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q86m-qjpm-vqcw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46591

Advisory: Apache Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation, allowing Cypher injection (incomplete remediation…
IDs: CVE-2026-46591, GHSA-q86m-qjpm-vqcw
Record: https://patchnext.com/advisories/cve-2026-46591 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-neo4j 4.21.0, 4.18.3, 4.14.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-neo4j: affected >= 4.10.0, < 4.14.8; >= 4.15.0, < 4.18.3; >= 4.19.0, < 4.21.0; fixed in 4.21.0, 4.14.8, 4.18.3

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-neo4j: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-neo4j.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q86m-qjpm-vqcw (GitHub-reviewed advisory GHSA-q86m-qjpm-vqcw lists affected ranges: Maven org.apache.camel:camel-neo4j >=4.10.0 =4.15.0 =4.19.0 <4.21.0)

Commands are suggestions: review each one before running it.