CVE-2026-40022

When authentication is enabled on the Apache Camel embedded HTTP server or embedded management server (camel-platform-http-main) and a non-root context path such as /api or /admin is configured via camel.server.path or camel.management.path, the BasicAuthenticationConfigurer and JWTAuthenticationConfigurer classes derive the authentication path from properties.getPath() when camel.server.authenticationPath / camel.management.authenticationPath is not explicitly set. Combined with the Vert.x sub-router mounting model - the sub-router is mounted at path* and the authentication handler is registered inside the sub-router at the resolved path - this causes the authentication handler to match only the exact configured context path, not its subpaths. Unauthenticated requests to subpaths such as /api/route or /admin/observe/info therefore reach protected business routes and management endpoints without being challenged for credentials. The /observe/info endpoint can disclose runtime metadata such as the user, working directory, home directory, process ID, JVM and operating system information.

This issue affects Apache Camel: from 4.14.1 before 4.14.6, from 4.18.0 before 4.18.2.

Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, they are suggested to upgrade to 4.14.6. If users are on the 4.18.x LTS releases stream, they are suggested to upgrade to 4.18.2.

CVE-2026-40022 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.6, 4.18.2, 4.20.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-40022? CVE-2026-40022 is a high-severity security vulnerability in org.apache.camel:camel-platform-http-main (maven), affecting versions >= 4.14.1, < 4.14.6. It is fixed in 4.14.6, 4.18.2, 4.20.0.
2. How severe is CVE-2026-40022? CVE-2026-40022 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.camel:camel-platform-http-main are affected by CVE-2026-40022? org.apache.camel:camel-platform-http-main (maven) versions >= 4.14.1, < 4.14.6 is affected.
4. Is there a fix for CVE-2026-40022? Yes. CVE-2026-40022 is fixed in 4.14.6, 4.18.2, 4.20.0. Upgrade to this version or later.
5. Is CVE-2026-40022 exploitable, and should I be worried? Whether CVE-2026-40022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40022?
   • Upgrade org.apache.camel:camel-platform-http-main to 4.14.6 or later
   • Upgrade org.apache.camel:camel-platform-http-main to 4.18.2 or later
   • Upgrade org.apache.camel:camel-platform-http-main to 4.20.0 or later