The Camel-Platform-HTTP component in Apache Camel mistakenly determines whether an endpoint should operate in proxy mode by checking if its configured path begins with the string 'proxy'. When an endpoint path only starts with those characters—such as 'proxyStatus', 'proxying', or 'proxy-config'—it is incorrectly treated as a proxy endpoint, even though the developer did not intend this. The unintended proxy setting allows the endpoint to forward incoming requests to arbitrary backends, creating a request‑forgery primitive and exposing whatever resources the forwarding target can reach.

Apache Camel versions prior to 4.18.5 in the 4.18.x LTS stream, prior to 4.22.1 in the 4.22.x LTS stream, and all releases from 4.0.0 up to those points are affected. The flaw is present in the Camel-Platform-HTTP component across those versions, meaning any deployment that uses the affected Camel distribution without upgrading or renaming paths that begin with 'proxy' is vulnerable.

The CVSS score of 4.8 indicates a moderate severity. EPSS data is missing, and the vulnerability is not listed in the CISA KEV catalog, suggesting that major public exploitation is not yet documented. Exploitation requires an attacker to target an endpoint with a path beginning with 'proxy' or to influence the configuration of a Camel instance. Because the fault lies in access control logic rather than a binary flaw or code execution path, the likelihood of remote exploitation depends on the exposure of the endpoint to external traffic and the ability to manipulate the configuration. The vulnerability remains controllable only by designers who can modify Camel routes or deployment configuration.