CVE-2026-80343
Improper Handling of Case Sensitivity vulnerability in Apache Camel Netty HTTP component
CVE-2026-80343: Improper Handling of Case Sensitivity vulnerability in Apache Camel Netty HTTP component. Not in the CISA KEV catalog.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
CVE-2026-80343 at a glance
- CISA KEV
- Not listed (catalog checked )
- Highest advisory severity
- High
- CVSS base score
- 8.2 (Apache), 8.2 (Red Hat)
- Weakness
- CWE-178
- Fixed releases
- Apache: 4.18.5, 4.22.1
- VulniPulse record
- Published · Updated
Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-80343; bulletin-wide values are not repeated here.
Is CVE-2026-80343 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-80343 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-80343?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 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. (Apache)
- Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
Vendor advisory comparison
Apache
1 advisory- Advisory severityHigh8.2
High [CVE-2026-80343] Improper Handling of Case Sensitivity vulnerability in Apache Camel Netty HTTP component
CVE-2026-80343Source published Source updated
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…
- Affected products in this advisory
- Apache Camel Netty
- Source-reported affected versions
- 4.0.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- 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.
- 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.
1 more entries in the full advisory.
Red Hat
1 advisory- Advisory severityHigh8.2
High [CVE-2026-80343] Security constraint bypass via case sensitivity mismatch
CVE-2026-80343Source published Source updated
Security constraint bypass via case sensitivity mismatch. Red Hat rates this important (CVSS 8.2). Weakness: CWE-178. Affected products named by the advisory: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.
- Related products — impact not confirmed
- Red Hat build of Apache Camel 4 for Quarkus 3
- Red Hat build of Apache Camel for Spring Boot 4
- Red Hat Fuse 7
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Browse the latest tracked CVEs or the CVEs listed in CISA KEV.
Android app · Google Play
Turn CVE research into alerts on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.