CamelApplication · Apache
CVE-2026-47323
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 · uneditedCamel-CXF and Camel-Knative Message Header Injection via Missing Inbound Filtering The CXF and Knative HeaderFilterStrategy implementations (CxfRsHeaderFilterStrategy in camel-cxf-rest, CxfHeaderFilterStrategy in camel-cxf-transport, and KnativeHttpHeaderFilterStrategy in camel-knative-http) only filter outbound Camel-internal headers via setOutFilterStartsWith, while not configuring inbound filtering via setInFilterStartsWith. As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelExecCommandExecutable, CamelFileName) via HTTP requests to CXF-RS or CXF-SOAP endpoints. When a route forwards messages from these endpoints to header-driven components such as camel-exec or camel-file, the injected headers override configured values, enabling remote code execution or arbitrary file writes. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.18.0 before 4.14.6, from 4.15.0 before 4.18.2. Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.2. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.
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 confidenceApache Camel CXF and Knative header filter strategies lack inbound filtering configuration, allowing unauthenticated attackers to inject Camel-internal headers (e.g., CamelExecCommandExecutable, CamelFileName) via HTTP requests. When routes forward to header-driven components like camel-exec or camel-file, these injected headers override configured values, enabling remote code execution or arbitrary file writes.
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
>= 3.18.0, < 4.14.6>= 4.15.0, < 4.18.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Apache Camel versionLocate the camel-core JAR file in your deployment (typically in the lib or dependencies folder) and examine its version, or run: java -jar camel-core-*.jar --version or check your build manifest (META-INF/MANIFEST.MF) for the Bundle-Version attribute.Affected if Version is >= 3.18.0 and < 4.14.6, or >= 4.15.0 and < 4.18.2
-
Identify CXF or Knative HeaderFilterStrategy usageSearch your application code and configuration for instances of org.apache.camel.component.cxf.CxfHeaderFilterStrategy or org.apache.camel.component.knative.KnativeHeaderFilterStrategy. Also check any XML/YAML route definitions referencing these filter classes.Affected if Either CXF or Knative HeaderFilterStrategy is in use without custom inbound filtering configured
-
Verify routes use vulnerable header-driven componentsReview your Camel routes (in Java, XML, or YAML configuration) and identify if any routes consume headers from CXF or Knative sources and pass them to camel-exec or camel-file components. Search for routes containing <route> with <from uri="cxf:*..."> or <from uri="knative:..."> combined with <to uri="exec:..."> or <to uri="file:...">.Affected if Routes combine CXF/Knative inbound endpoints with camel-exec or camel-file producers using header values
-
Inspect inbound header filter configurationExamine your HeaderFilterStrategy bean definitions (in Spring, CDI, or Blueprint XML) for the presence of setInFilterStartsWith method call or an InFilter pattern configured. Check if the filter explicitly removes internal Camel headers from inbound requests.Affected if No setInFilterStartsWith is configured, or the InFilter pattern does not block Camel-internal headers like CamelExecCommandExecutable or CamelFileName
You are affected if your Apache Camel version falls within the vulnerable range AND you use CXF or Knative HeaderFilterStrategy with routes that pass inbound headers to camel-exec or camel-file components without inbound filtering configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.14.64.18.2
Upgrade Apache Camel to version 4.19.0, or to LTS versions 4.18.2 or 4.14.6 as appropriate for the deployment branch.
4.19.0 for latest; 4.18.2 for 4.18.x LTS; 4.14.6 for 4.14.x LTS
- Identify the current Apache Camel version in use by checking the project's dependency management (Maven pom.xml, Gradle build file, or container image tags)
- Determine which LTS stream the current version belongs to: 4.14.x, 4.15.x-4.18.x, or 3.18.x-3.x
- If on 4.14.x stream: upgrade Apache Camel to version 4.14.6
- If on 4.15.x through 4.18.x stream: upgrade Apache Camel to version 4.18.2
- If on 3.18.x through 3.x stream: upgrade to 4.14.6 or later (4.19.0 recommended for latest fixes)
- If using 4.19.0 as a fresh install: ensure all Camel components are aligned to version 4.19.0
- Rebuild and redeploy the application
- Verify the fix by testing that injected Camel-internal headers (e.g. CamelExecCommandExecutable, CamelFileName) are rejected on inbound CXF-RS, CXF-SOAP, or Knative HTTP endpoints
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Camel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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