Skip to content
Fencer Intel
high 8.2

CVE-2026-80343 json

Apache Camel: Camel-Netty-HTTP Security Constraint Bypass via Case-Sensitive Context-Path Matching

published 23d ago modified 8d ago also EUVD-2026-104214

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.camel:camel-netty-http 4.18.5, 4.22.1, 4.23.0
  • Apache Software Foundation Apache Camel 4.18.5, 4.22.1, 4.23.0

Is CVE-2026-80343 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-80343 updated cvss 8.2

org.apache.camel/camel-netty-http: Apache Camel Netty HTTP: Security constraint bypass via case sensitivity mismatch

  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-netty-http 4.18.4.redhat-00007 Red Hat build of Apache Camel for Spring Boot 4 camel-netty-http 4.18.4.redhat-00007
    affected: workaround, no fix available
  • Red Hat Build of Apache Camel 3.40.1.redhat camel-netty-http 4.22.1.redhat-00008
    fixed: vendor fix RHSA-2026:98783
  • Red Hat Build of Apache Camel 3.40.1.redhat re2j 1.8, jimfs 1.1, jna 5.8.0, bcel 6.7.0, gax 2.81.0, s3 2.54.13, +1617 more
    not affected: vulnerable code not present
  • Red Hat Fuse 7 camel-netty-http 4.18.4.redhat-00007
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
23d ago

Exploit prediction

0.93% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-netty-http
>=4.0.0, <4.18.5
>=4.19.0, <4.22.1
4.18.5
4.22.1
4.23.0

Affected products

  • Apache Software Foundation Apache Camel

Classification

Weakness
  • CWE-178 Improper Handling of Case Sensitivity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.