Severity:
CVSS 3.1: 8.2 (high) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-netty-http) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-netty-http) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-netty-http) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-netty-http) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-netty-http) 4.23.0 unaffected
Description:
Improper Handling of Case Sensitivity vulnerability in Apache Camel Netty HTTP
component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before
4.22.1.
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.
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. The constraint now matches the request path
with the same case rules the dispatch uses, so the two can no longer disagree.
For deployments that cannot upgrade immediately, place the authorization
decision in front of the Camel consumer, for example in a reverse proxy that
normalises the request path before forwarding.
Solution:
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. The constraint now matches the request path
with the same case rules the dispatch uses, so the two can no longer disagree.
Work Arounds:
For deployments that cannot upgrade immediately, place the authorization
decision in front of the Camel consumer, for example in a reverse proxy that
normalises the request path before forwarding.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-80343.html
https://issues.apache.org/jira/browse/CAMEL-24412
https://github.com/apache/camel/pull/25578
https://github.com/apache/camel/pull/25761
https://github.com/apache/camel/pull/25762
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-80343
