Read the docs
TI-2026-34251 Aliases CVE-2026-46591GHSA-q86m-qjpm-vqcw

Apache Camel: Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header…

Priority MEDIUM 42CWE-943Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub.

Summary

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 header is itself Camel-prefixed and is filtered by the HTTP header-filter strategy, so a plain HTTP client cannot set it directly; the issue is reachable through routes that deliberately or inadvertently carry untrusted data into that header. This issue affects Apache Camel: from 4.10.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, do not populate the CamelNeo4jMatchProperties map from untrusted input: validate or allow-list the property names (for example against ^[A-Za-z_][A-Za-z0-9_]*$) before the Neo4j producer, and ensure that any consumer feeding such a route filters inbound Camel* / camel* headers so the match header cannot be supplied by an external sender.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0055 46th percentileScored 2026-11-07
Fix Fixed Apache Camel (Apache Software Foundation): 4.14.8, 4.18.3, 4.21.0org.apache.camel:camel-neo4j (Maven): 4.14.8, 4.18.3, 4.21.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Camel4.10.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.04.14.8, 4.18.3, 4.21.0Patch availableCNA
—org.apache.camel:camel-neo4j (Maven)4.10.0 to before 4.14.84.14.8Patch availableGHSA-q86m-qjpm-vqcw
—org.apache.camel:camel-neo4j (Maven)4.15.0 to before 4.18.34.18.3Patch availableGHSA-q86m-qjpm-vqcw
—org.apache.camel:camel-neo4j (Maven)4.19.0 to before 4.21.04.21.0Patch availableGHSA-q86m-qjpm-vqcw
  • Apache Camel VendorApache Affected 4.10.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0 Fixed in 4.14.8, 4.18.3, 4.21.0 Patch available CNA
  • org.apache.camel:camel-neo4j (Maven) Vendor— Affected 4.10.0 to before 4.14.8 Fixed in 4.14.8 Patch available GHSA-q86m-qjpm-vqcw
  • org.apache.camel:camel-neo4j (Maven) Vendor— Affected 4.15.0 to before 4.18.3 Fixed in 4.18.3 Patch available GHSA-q86m-qjpm-vqcw
  • org.apache.camel:camel-neo4j (Maven) Vendor— Affected 4.19.0 to before 4.21.0 Fixed in 4.21.0 Patch available GHSA-q86m-qjpm-vqcw

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*4.10.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0VulnerableApache
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* Versions 4.10.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0 Vulnerable ·Apache

Remediation

  • Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.14.8, 4.18.3, 4.21.0
  • Fix · GHSA-q86m-qjpm-vqcw org.apache.camel:camel-neo4j (Maven) Fixed in 4.14.8 Advisory →
  • Fix · GHSA-q86m-qjpm-vqcw org.apache.camel:camel-neo4j (Maven) Fixed in 4.18.3 Advisory →
  • Fix · GHSA-q86m-qjpm-vqcw org.apache.camel:camel-neo4j (Maven) Fixed in 4.21.0 Advisory →

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Apache Camel 4.14.8, 4.18.3, 4.21.0

    14 records Highest priority Priority MEDIUM 7 MEDIUM, 7 LOW

    Other records, highest priority first

    • TI-2026-35614 Improper input validation in Apache CamelPriority MEDIUM 50
    • TI-2026-34159 Improper input validation in Apache CamelPriority MEDIUM 50
    • TI-2026-34157 Improper input validation in Apache CamelPriority MEDIUM 50

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-46591
  2. 2026-10-03 Alias added: GHSA-q86m-qjpm-vqcw

References

  • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
  • TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
  • TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
  • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
  • TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
  • TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
See all 116 →

Sources