Camel-CXF and Camel-Knative Message Header are Vulnerable to Injection via Missing Inbound Filtering

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-47323: 19.56% estimated exploitation activity in the next 30 days; percentile 97.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Camel-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…

Published by the source

19 May 2026, 15:31 UTC

Last modified by the source

5 Oct 2026, 18:39 UTC

Source last checked

26 Oct 2026, 16:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8364-hfqj-pwm6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47323

Advisory: Camel-CXF and Camel-Knative Message Header are Vulnerable to Injection via Missing Inbound Filtering
IDs: CVE-2026-47323, GHSA-8364-hfqj-pwm6
Record: https://patchnext.com/advisories/cve-2026-47323 (revision 1, source checked 26 Oct 2026, 16:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-cxf-rest 4.18.2, 4.14.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-cxf-rest: affected >= 3.18.0, < 4.14.6; >= 4.15.0, < 4.18.2; fixed in 4.18.2, 4.14.6

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-cxf-rest: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-cxf-rest.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8364-hfqj-pwm6 (GitHub-reviewed advisory GHSA-8364-hfqj-pwm6 lists affected ranges: Maven org.apache.camel:camel-cxf-rest >=3.18.0 =4.15.0 <4.18.2)

Commands are suggestions: review each one before running it.