Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-46592 – Confused Deputy / Unauthorized SOAP Operation Invocation – Apache Camel CXF 4.0….

Be the first to know when new zero-days emerge:

Summary

CVE-2026-46592 is an Improper Input Validation / Confused Deputy vulnerability in the Apache Camel CXF SOAP component, affecting versions 4.0.0 through 4.20.x. An unauthenticated remote attacker can inject a crafted HTTP header into a Camel route that bridges an HTTP consumer to a CXF SOAP producer, redirecting the backend SOAP service to invoke an attacker-chosen WSDL operation instead of the one the route intended. The vulnerability is rated High severity with a CVSS v3.1 score of 7.5.

Technical details

  • Root cause: The camel-cxf producer resolves which SOAP operation to invoke from the operationName and operationNamespace Exchange headers. The constant values for these headers (CxfConstants.OPERATION_NAME / OPERATION_NAMESPACE) were the plain strings operationName / operationNamespace — names that do not begin with the Camel/ prefix. As a result, HttpHeaderFilterStrategy, which only blocks headers in the Camel namespace, passed them through from an inbound HTTP request directly into the Exchange.
  • Trigger conditions: Exploitable only in Camel routes that bridge an HTTP consumer (e.g., platform-http, camel-servlet, camel-jetty, camel-undertow) to a cxf: producer, where the HTTP consumer endpoint is reachable by untrusted clients.
  • Attack vector: An unauthenticated HTTP client sends a request carrying a crafted operationName header to the exposed Camel HTTP endpoint. The CxfProducer resolves and invokes the attacker-specified WSDL operation on the backend SOAP service — a classic confused-deputy redirection requiring no credentials.
  • Impact: The attacker can cause the backend SOAP service to execute WSDL operations other than those intended by the route — for example, substituting a read-only operation with a destructive one — and can extract confidential data returned by the backend service (CVSS C:H). The camel-cxfrs component is also affected, as it shares the same unqualified header constants through the camel-cxf-common module.

Affected software

  • Apache Camel 4.0.0 through 4.14.7
  • Apache Camel 4.15.0 through 4.18.2
  • Apache Camel 4.19.0 through 4.20.x
  • The camel-cxfrs component is also affected via shared constants in camel-cxf-common

Severity

CVSS v3.1 Base Score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Upgrade to Apache Camel 4.21.0 (latest stable). After upgrading, operation-selection headers are renamed to CamelCxfOperationName / CamelCxfOperationNamespace and are filtered at transport boundaries. Consult the 4.21 upgrade guide for the cross-transport carrier-header pattern.
  • LTS (4.14.x) users: Upgrade to 4.14.8.
  • 4.18.x users: Upgrade to 4.18.3.
  • If immediate upgrade is not possible: Strip the operationName and operationNamespace headers from all untrusted HTTP ingress before the cxf: producer node in the route, and set the operation name explicitly from a trusted source within the route definition.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge