CVE-2026-80343
8.2HighPublished 19 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-178
Impact
Unauthenticated remote attackers can bypass path-based security constraints to access protected endpoints. They only need network access to send an HTTP request with altered path casing to the consumer.
Root cause
The camel-netty-http security constraint enforces case-sensitive path matching while endpoint routing does not, allowing case-altered requests to evade checks but still reach the target.
Affected systems
Apache Camel 4.0.0 before 4.18.5, and 4.19.0 before 4.22.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Fix & remediation
Upgrade to Apache Camel 4.23.0, 4.22.1, or 4.18.5. If patching must wait, enforce authorization upstream via a reverse proxy that normalizes request path casing before forwarding to Camel.
$ mvn dependency:tree -Dincludes=org.apache.camel:camel-netty-httpAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.