dbcve.org
CamelApplication · Apache

CVE-2025-66169

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-14
Fix available
A fix is available. Upgrade to 4.10.8 / 4.14.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cypher injection vulnerability in Apache Camel's camel-neo4j component allows attackers to manipulate Neo4j graph database queries through unsanitized input, similar to SQL injection but targeting the Cypher query language used by Neo4j.

MitigationUpgrade Apache Camel to version 4.10.8, 4.14.3, or 4.17.0 (depending on your branch) to resolve this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.10.0, < 4.10.8>= 4.14.0, < 4.14.3>= 4.15.0, < 4.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version
    Check your project's Maven pom.xml for the camel-bom or individual camel-core version, or run: mvn dependency:tree | grep camel-core. In runtime deployments, check the lib folder for camel-core-{version}.jar
    Affected if Version is 4.10.0-4.10.7, 4.14.0-4.14.2, or 4.15.0-4.16.x (before 4.17.0)
  2. Check for camel-neo4j dependency
    Run: mvn dependency:tree | grep neo4j, or inspect your build artifacts for camel-neo4j-{version}.jar
    Affected if The camel-neo4j component is present in your dependencies
  3. Identify Neo4j route definitions
    Search your codebase for Neo4j endpoint URIs in route definitions: look for 'neo4j://' in XML, YAML, or Java DSL route files. Also check for beans of type Neo4jComponent or Neo4jEndpoint
    Affected if Routes configure a Neo4j endpoint
  4. Inspect query parameter usage
    Review the Neo4j route code for dynamic values in Cypher queries, particularly header expressions, simple expressions, or parameters passed from external sources (such as: ${header.name}, $simple{body.field}, or query parameters from incoming messages)
    Affected if User-controlled or dynamic input is passed directly to Cypher query parameters without using parameterized queries

You are affected if you run Apache Camel in the vulnerable version range AND use the camel-neo4j component with dynamic input in Cypher queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.10.8 / 4.14.3 / 4.17.0 or later
Fixed in 4.10.84.14.34.17.0
Interim mitigation

Upgrade Apache Camel to version 4.10.8, 4.14.3, or 4.17.0 (depending on your branch) to resolve this vulnerability.

Recommended fix High confidence

Upgrade to Apache Camel 4.10.8, 4.14.3, or 4.17.0 depending on your current branch

  1. Identify the current Apache Camel version in use (check pom.xml, build.gradle, or container image tags)
  2. Update the Camel dependency version to the appropriate fixed release: 4.10.8 for 4.10.x users, 4.14.3 for 4.14.x users, or 4.17.0 for 4.15.x/4.16.x users
  3. In Maven projects, update the camel-bom and camel-neo4j dependency versions in pom.xml
  4. Run build and tests to verify the upgrade does not introduce regressions
  5. Redeploy the updated application
Caveat No specific breaking changes mentioned for this security fix; standard upgrade testing recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data