CVE-2026-85316: Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching
Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The component decided whether an endpoint ran in proxy mode by testing whether its configured path started with the string proxy, rather than by matching the path exactly. Any endpoint whose path merely begins with those characters - proxyStatus, proxy-config, proxying and so on - therefore became a proxy endpoint without the route author asking for it. A proxy endpoint forwards requests onward, so an endpoint that was intended to serve its own content instead relays traffic on behalf of whoever calls it, which is both a request forgery primitive and an exposure of whatever the forwarding path can reach.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Proxy mode is now selected by an exact path match rather than by prefix. For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel: Camel-Platform-HTTPto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camel: Camel-Platform-HTTPto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camel: Camel-Platform-HTTPto a version that resolves this vulnerability.Fixed in 4.22.1 - Configuration
For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.
Apache Camel: Camel-Platform-HTTP endpoint path = must not begin with proxy
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using the Apache Camel Platform HTTP component are exposed if they run Apache Camel 4.0.0 through versions before 4.18.5, or 4.19.0 through versions before 4.22.1, and have an endpoint path beginning with "proxy" that was not intended to operate as a proxy.
What does an attacker need to exploit this issue?
An attacker needs network access to call an affected endpoint. No privileges or user interaction are required, but successful abuse depends on what destinations or resources the unintended forwarding path can reach.
How can I determine whether an endpoint is affected?
Review configured Platform HTTP endpoint paths for names beginning with "proxy", such as "proxyStatus", "proxy-config", or "proxying". On affected versions, those paths are treated as proxy endpoints even when proxy behavior was not intended.
What can I do if I cannot upgrade immediately?
Rename every endpoint path that begins with "proxy" unless it is intentionally meant to be a proxy endpoint. The permanent fix is to upgrade to Apache Camel 4.18.5 for the 4.18.x LTS stream, 4.22.1 for the 4.22.x LTS stream, or 4.23.0.