Live › vulnerability › CVE-2026-80343
Go to dashboardThe camel-netty-http component checks its security constraint with a case-sensitive path match, but routing dispatches without that rule. A caller who changes the case of a path character can reach a protected endpoint without satisfying the constraint.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that run Apache Camel's camel-netty-http consumer and rely on its security constraint to protect routes by path. Exposure depends on the configured context path and on whether the consumer can receive requests from callers who should not reach the protected route. Teams not using camel-netty-http or running a fixed version can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-netty-http) and confirm whether it falls in 4.0.0 to before 4.18.5, or 4.19.0 to before 4.22.1.4.23.0.4.18.5.4.22.1.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-80343")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.