CyberSecBulletin
CVE-2026-80343NVD status: Analyzed

Apache Camel: Improper Handling of Case Sensitivity

Published Updated By the CyberSecBulletin desk

CVE-2026-80343 is a high-severity improper handling of case sensitivity vulnerability in Apache Camel from Apache, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.18.5, 4.22.1 as the first without the flaw, so updating Apache Camel to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.93% chance of exploitation within 30 days, higher than 61% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Apache Camel to 4.18.5 or 4.22.1, whichever matches your release line, or a later version.
  2. Update Camel to 4.18.5 or 4.22.1, whichever matches your release line, or a later version.
  3. Read the advisory on camel.apache.org for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache Camel4.0.0 up to, but not including, 4.18.5; 4.19.0 up to, but not including, 4.22.14.18.5, 4.22.1
ApacheCamel4.0.0 up to, but not including, 4.18.5; 4.19.0 up to, but not including, 4.22.14.18.5, 4.22.1

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
LowLimited modification of data is possible.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. Scored by CNA (apache.org).

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Handling of Case Sensitivity

The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.

How developers prevent this class of flaw

  • Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
  • Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

More Improper Handling of Case Sensitivity vulnerabilities (CWE-178)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Apache Camel

All Apache Camel vulnerabilities

Recent Improper Handling of Case Sensitivity vulnerabilities

Spotted an error? Tell us.