cve.bz

CVE-2026-80343 apache camel: Improper Handling of Case Sensitivity

8.2 highEPSS 0.9%Fix available

High (8.2) in apache camel. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.9% (unchanged from 0.9% a week ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-178 Improper Handling of Case Sensitivity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-80343 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80343?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80343?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80343 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-80343

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-80343](https://cve.bz/cve/badge/CVE-2026-80343.svg)](https://cve.bz/cve/CVE-2026-80343)

HTML:

<a href="https://cve.bz/cve/CVE-2026-80343"><img src="https://cve.bz/cve/badge/CVE-2026-80343.svg" alt="CVE-2026-80343"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important impact because an unauthenticated remote attacker can circumvent endpoint security constraints without prior privileges, gaining unauthorized access to protected routes. In Red Hat environments, this issue primarily affects integration services using Camel Netty HTTP that rely directly on its internal context-path matching for authorization. Deployments that offload authorization decisions to an external API gateway or reverse proxy are not directly exposed to this constraint mismatch.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3camel-netty-httpAffected
Red Hat build of Apache Camel for Spring Boot 4camel-netty-httpAffected
Red Hat Fuse 7camel-netty-httpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80343.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-80343 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-80343 (Apache Camel camel-netty-http): security constraint case-sensitivity bypass — altering the path case skips t…

References

Check your stackJSON