CVE-2026-46591 apache · camel

Apache Camel: Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cyphe

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v3.1 severity
8.2High
EPSS · exploitation likelihood
0.55% Probability within 30 daysPercentile 46.9
EPSS trend
Unchanged Since 2026-11-13
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
LowFewer obstacles to exploitation
Privileges required
NoneNo authentication required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Availability not established No explicit exploit maturity assessment View exploit evidence
How to read the colors & trend
Higher exposureElevatedModerateLower exposureUnknown / unassessed

CVSS colors follow its reported severity. Attack-factor colors describe each requirement, not an overall risk rating. Gray also covers absence from KEV; absence does not establish safety.

EPSS display bands: below 1% blue, 1–10% amber, 10–50% orange, 50% and above red. These are presentation bands, not FIRST severity categories. The trend compares daily EPSS probabilities, not percentile ranks; “pp” means percentage points. The sparkline shows relative movement, with its vertical scale fitted to the observed scores.

Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

1 rule identified Verified 2026-11-10 View rules & research details →

WAF protection does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC assessment

CISA ADP · Assessed 2026-07-06 · SSVC 2.0.3

Exploitation
None reported
Automatable
Yes
Technical Impact
Partial

Stakeholder-Specific Vulnerability Categorization records CISA’s assessment of exploitation, automation, and technical impact. “None reported” reflects the assessment date; it does not establish that no exploit exists. View SSVC source details.

On this page

CVE Details

  • Protection status: Protected by Atomicorp rules · About protection statuses
  • CVE: CVE-2026-46591
  • Name: Apache Camel: Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cyphe
  • Severity: High
  • CVSS: 8.2 (v3.1) (High)
  • CVSS version: 3.1
  • CVSS source: CISA ADP
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: Low
    • Integrity impact: High
    • Availability impact: None
  • CWE: CWE-943 — Improper Neutralization of Special Elements in Data Query Logic
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-676 (opens in a new tab)
  • Vendor: apache
  • Vulnerable product: camel
  • CVE published: 2026-07-06
  • CVE last modified: 2026-10-25
  • Affected versions (NVD configurations):
    • camel: >= 4.10.0, < 4.14.8
    • camel: >= 4.15.0, < 4.18.3
    • camel: >= 4.19.0, < 4.21.0
  • EPSS: 0.0055; 46.9th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
  • Latest Update: 2026-11-10
  • Selected Rule IDs observed: 390719
  • Matching rules: 1; rules with blocking actions: 1
  • Would-block Rule IDs: 390719
  • Request surfaces inspected: Request headers
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v3.1 · CISA ADP

  • Base score: 8.2
  • Base severity: HIGH
  • Exploitability subscore: 3.9
  • Impact subscore: 4.2
  • Assessment type: Secondary
  • Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • Full vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: Low
    • Integrity impact: High
    • Availability impact: None
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)

CISA SSVC assessments

These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.

  • Provider: CISA ADP
  • Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • SSVC version: 2.0.3
  • Role: CISA Coordinator
  • Assessment timestamp: 2026-07-06T19:20:49.095923Z
  • Exploitation: none
  • Automatable: yes
  • Technical Impact: partial
  • Source: CISA ADP in the CVE record (opens in a new tab)

Vulnerable CPE configurations

  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 4.10.0
    • Version end (exclusive): 4.14.8
    • NVD match criteria ID: CD453DD1-65B8-49D0-BB84-3D585163C326
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 4.15.0
    • Version end (exclusive): 4.18.3
    • NVD match criteria ID: 0AEE4159-4465-4ACD-B94A-1E4682C85270
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 4.19.0
    • Version end (exclusive): 4.21.0
    • NVD match criteria ID: 1C2A1A7A-FADC-470F-8265-FA126AFD94ED

Vulnerability Description

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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (390719 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.14.8.
    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.18.3.
    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.21.0.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.14.8 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.18.3 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.21.0 or later.
  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .