CVE-2026-80343
Camel-Netty-HTTP: security constraint bypass - the security constraint matched the request path case sensitively while dispatch to the route did not, so altering the case of a path segment skipped the constraint and still reached the endpoint
Description
The camel-netty-http security constraint compared the request path against the configured context path using a case-sensitive match, while the routing that dispatches the request to the endpoint did not apply the same rule. The two comparisons therefore disagreed for any path whose case differed from the configured value. An external caller could alter the case of a character in a path segment so that the security constraint no longer recognised the path as protected, while the request still dispatched to the same endpoint. The result is that the constraint is skipped and the protected route is reached without satisfying it. No credential, prior access or special configuration is required beyond being able to send a request to the consumer.
Mitigation
Credit
This issue was discovered by Claude Security Scan Tool
Notes
The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24412 refers to the various commits that resolved the issue, and has more details.
The fix was merged on main in https://github.com/apache/camel/pull/25578 (commit 9c18465443a0df60179e6abf96f7794983cd0637), backported to camel-4.22.x in https://github.com/apache/camel/pull/25761 (commit ccd49cc5049113c8be976ecef3d581da112b9918) and to camel-4.18.x in https://github.com/apache/camel/pull/25762 (commit 1d280e815f350bbeb8888150cfb5a3d8eca3c7b9).
The issue is classified as CWE-178 Improper Handling of Case Sensitivity. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later.