CVE-2026-40022 Details
Description
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.
A vulnerability exists in Apache Camel's embedded HTTP server and management server (camel-platform-http-main) versions 4.14.1 prior to 4.14.6 and 4.18.0 prior to 4.18.2. When authentication is enabled and a non-root context path such as /api or /admin is set, the authentication path is derived from the general properties unless explicitly specified. This, combined with the Vert.x sub-router model, leads to the authentication handler only matching the exact context path, not its subpaths. As a result, unauthenticated requests to subpaths can access protected business routes and management endpoints without credential verification. The /admin/observe/info endpoint, in particular, can expose sensitive runtime metadata.
Users are advised to upgrade to Apache Camel version 4.20.0, 4.14.6 (for 4.14.x LTS releases), or 4.18.2 (for 4.18.x LTS releases).
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 27, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://access.redhat.com/errata/RHSA-2026:17668 | redhat-SADP | |
| https://access.redhat.com/security/cve/CVE-2026-40022 | redhat-SADP | |
| https://bugzilla.redhat.com/show_bug.cgi?id=2463178 | redhat-SADP | |
| https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40022.json | redhat-SADP | |
| http://www.openwall.com/lists/oss-security/2026/04/26/5 | CVE | Mailing ListThird Party Advisory |
| https://camel.apache.org/security/CVE-2026-40022.html | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-288 | Authentication Bypass Using an Alternate Path or Channel | [email protected] |
| CWE-551 | Incorrect Behavior Order: Authorization Before Parsing and Canonicalization | redhat-SADP |
Affected Products
| Product | Versions |
|---|---|
| apache camel | >= 4.14.1, < 4.14.6 >= 4.15.0, < 4.18.2 |
CPE
Remediation
| |
Change History
8 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 28, 2026 | Initial Analysis | [email protected] |
| Apr 27, 2026 | CVE Modified | CISA-ADP |
| Apr 27, 2026 | New CVE Received | [email protected] |
| Apr 27, 2026 | CVE Modified | CVE |