---
id: "CVE-2026-80343"
kind: "vulnerability"
aliases: ["CVE-2026-80343"]
title: "Apache Camel Netty HTTP: path case mismatch skips security constraints"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "camel-netty-http", "java", "package", "self-hosted"]
not_affected_if: ["fixed-version", "not-using-camel-netty-http"]
published_at: "2026-10-19T11:17:21+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T03:04:22+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80343", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# Apache Camel Netty HTTP: path case mismatch skips security constraints

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Camel version in the project build file (for example `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.
- Look for camel-netty-http consumers that use a security constraint or context path to protect routes.

## Fix

- Upgrade Apache Camel to `4.23.0`.
- Users on the 4.18.x LTS stream: upgrade to `4.18.5`.
- Users on the 4.22.x LTS stream: upgrade to `4.22.1`.
- If an immediate upgrade is not possible, enforce authorization in a reverse proxy that normalises request paths before forwarding.

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-80343

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_