CVE-2025-66169VulnerabilityPublished 14 Jan 2026Updated 15 Jan 2026

CVE-2025-66169: Apache Camel Neo4j · Cypher Injection

Affects Apache Camel Neo4jSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.17.0 : update Apache Camel Neo4j when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.17.0, 4.14.3, 4.10.8

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache to 4.17.0, 4.14.3 or 4.10.8.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Camel Neo4j	Affected >=4.10.0 <4.10.8 >=4.14.0 <4.14.3 >=4.15.0 <4.17.0	Fixed in 4.17.0 4.14.3 4.10.8
Mavenorg.apache.camel/camel-neo4j`pkg:maven/org.apache.camel/camel-neo4j`Other threats	Affected =4.10.0 =4.14.0 =4.15.0	Fixed in–
MavenApache Software Foundation/org.apache.camel:camel-neo4j`pkg:maven/Apache Software Foundation/org.apache.camel:camel-neo4j`Other threats	Affected >=4.10.0 <4.10.8 >=4.14.0 <4.14.3 >=4.15.0 <4.17.0	Fixed in 4.10.8 4.14.3 4.17.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Apache Camel to the patched versions: 4.10.8 for 4.10.x LTS, 4.14.3 for 4.14.x LTS, or 4.17.0 for 4.15.x and later branches. 2. Implement strict input validation and sanitization for all data inputs that are incorporated into Cypher queries to prevent injection of malicious payloads. 3. Employ parameterized queries or prepared statements where possible to separate code from data in Cypher query construction. 4. Monitor Neo4j query logs and Apache Camel integration logs for unusual or unexpected query patterns indicative of injection attempts. 5. Restrict network access to Neo4j and Apache Camel endpoints to trusted internal networks and enforce strong access controls. 6. Conduct security code reviews and penetration testing focused on injection vulnerabilities in the integration layer. 7. Educate developers and DevOps teams about secure coding practices specific to Cypher and graph database interactions. 8. Maintain an incident response plan to quickly address any detected exploitation attempts.

Description

Cypher Injection vulnerability in Apache Camel camel-neo4j component. This issue affects Apache Camel: from 4.10.0 before 4.10.8, from 4.14.0 before 4.14.3, from 4.15.0 before 4.17.0 Users are recommended to upgrade to version 4.10.8 for 4.10.x LTS and 4.14.3 for 4.14.x LTS and 4.17.0.

Impact

For European organizations, the Cypher Injection vulnerability poses a risk primarily to data integrity within Neo4j graph databases integrated via Apache Camel. Attackers exploiting this flaw could manipulate or corrupt critical business data, potentially disrupting analytics, decision-making, or operational processes dependent on graph data. Since the vulnerability requires no authentication or user interaction, it could be exploited remotely if the affected services are exposed or accessible internally. This risk is heightened in sectors relying heavily on graph databases for complex relationship mapping, such as finance, telecommunications, and public sector agencies. While confidentiality and availability are not directly impacted, integrity breaches can lead to compliance violations under GDPR if data accuracy is compromised. Additionally, undetected data manipulation could undermine trust in automated systems and analytics. The medium severity rating suggests moderate urgency but should not be underestimated given the potential for stealthy data tampering. Organizations with large-scale Neo4j deployments integrated with Apache Camel are particularly at risk.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 20:25 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats