CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NHigh (8.2) in apache camel. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
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.
--- 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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-netty-http | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-netty-http | Affected | |
| Red Hat Fuse 7 | camel-netty-http | Not 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.
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.