{“lastseen”:””,”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.\\n\\nThis issue affects Apache Camel: from 4.14.1 before 4.14.6, from 4.18.0 before 4.18.2.\\n\\nUsers 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.”,”published”:”2026-04-27T09:40:28.107Z”,”modified”:”2026-04-27T15:05:15.516Z”,”type”:”cve”,”title”:”Apache Camel Platform HTTP Main: Authentication Bypass on Non-Root Context Paths in camel main runtime”,”source”:”apache”,”references”:”https:\/\/camel.apache.org\/security\/CVE-2026-40022.html”,”id”:”CVE-2026-40022″,”bulletinFamily”:””,”cwe”:[“CWE-288″],”cvelist”:null,”sourceData”:”Apache Software Foundation Apache Camel Platform HTTP Main 4.14.1\\nApache Software Foundation Apache Camel Platform HTTP Main 4.18.0″,”sourceHref”:””,”cvss”:{“score”:8.2,”severity”:”HIGH”,”vector”:”CVSS:3.1\/AV:N\/AC:L\/PR:N\/UI:N\/S:U\/C:H\/I:L\/A:N”,”version”:”3.1″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”Apache Camel Platform HTTP Main”,”version”:”4.14.1″,”vendor”:”Apache Software Foundation”,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”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…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,8,77,12,15,13,7,11,5],"class_list":["post-49740","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-cve","tag-cvss","tag-cvss-82","tag-exploit","tag-high","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n