CVE-2026-80343
Description
A flaw was found in Apache Camel's Netty HTTP component. Due to inconsistent case-sensitivity handling, security constraint checks evaluate requested URL paths using case-sensitive matching while endpoint dispatch does not. A remote, unauthenticated attacker can exploit this discrepancy by altering the character casing in a request path to bypass access restrictions and reach protected endpoints.
Mitigation
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to align path normalization between security constraint checks and endpoint routing in Camel Netty Http consumers to eliminate case-handling discrepancies: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Netty Http builds), which perform a direct case-insensitive prefix comparison when stripping the context path during target extraction in HttpServerChannelHandler, closing HTTP request with altered character casing in URL path segments. Until patched, this is a concern on Apache Camel deployments using Camel Netty Http with security-constrained routes, so Place an upstream reverse proxy in front of the Camel consumer to normalize request path casing before forwarding, or relocate authorization enforcement in front of the consumer. These controls limit blast radius and contain exploitation, but they do not fix the underlying case sensitivity mismatch defect — apply the upstream patch to fully remediate.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.2 | N/A | 8.2 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
