CVE-2026-80343: Software Security Vulnerability Vulnerability
HIGHCVE-2026-80343 is a HIGH (CVSS 8.2) security vulnerability vulnerability (CWE-178: Improper Handling of Case Sensitivity) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-80343 at a Glance
Security Impact
CVSS: 8.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-80343
To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-80343, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree
Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-178: Improper Handling of Case Sensitivity, where the product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
References
Frequently Asked Questions
What is CVE-2026-80343?
Which Software versions are affected?
What version fixes CVE-2026-80343?
What is the CVSS score of CVE-2026-80343?
What CWE is associated with CVE-2026-80343?
How can I check Maven dependencies for CVE-2026-80343?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pvjg-pwh7-34pj",
"modified" : "2026-10-19T12:32:50Z",
"published" : "2026-10-19T12:32:50Z",
"aliases" : [ "CVE-2026-80343" ],
"details" : "Improper Handling of Case Sensitivity vulnerability in Apache Camel Netty HTTP component.\n\n\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\n\n\nThe 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.\n\n\n\nUpgrade 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" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80343"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25578"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25761"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25762"
}, {
"type" : "WEB",
"url" : "https://camel.apache.org/security/CVE-2026-80343.html"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/CAMEL-24412"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-178" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-19T11:17:21Z"
}
}