dbcve.org
CamelApplication · Apache

CVE-2026-40022

HIGH · 8.2 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 4.14.6 / 4.18.2 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authentication bypass in Apache Camel's embedded HTTP server where the BasicAuthenticationConfigurer and JWTAuthenticationConfigurer only match the exact configured context path (e.g., /api) rather than subpaths, allowing unauthenticated access to routes like /api/route or /admin/observe/info that can disclose runtime metadata.

MitigationUpgrade Apache Camel to version 4.14.6, 4.18.2, or 4.20.0 which contains the fix for proper subpath authentication matching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.14.1, < 4.14.6>= 4.15.0, < 4.18.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version
    Check your application's dependency management or running instance to determine the exact Apache Camel version in use. Common locations: Maven pom.xml, Gradle build file, or runtime banner if enabled.
    Affected if The installed version falls within >= 4.14.1, < 4.14.6 OR >= 4.15.0, < 4.18.2.
  2. Verify if authentication is enabled
    Inspect your Camel application configuration for BasicAuthentication or JWTAuthentication configuration. Look for camel.server.auth.type, camel.security or similar authentication settings in your application.properties, application.yaml, or Spring/XML configuration files.
    Affected if Authentication is explicitly enabled (not set to false or disabled).
  3. Determine the context path configuration
    Check the camel.servlet.context-path property or any server path configuration in your application properties/yaml file. Look for values like /api, /admin, or any non-root path prefix.
    Affected if A non-root context path is configured (e.g., /api, /admin, /custompath).
  4. Check for exposed management endpoints
    Attempt to access the /admin/observe/info endpoint (or similar management paths under your configured context) without authentication. Use curl or a browser: curl -k https://<host>:<port>/<context-path>/admin/observe/info
    Affected if The endpoint returns sensitive runtime metadata (user, working directory, home directory, PID, JVM/OS information) without requiring authentication.
  5. Inspect authentication path configuration
    Review your authentication configuration files for camel.server.authenticationPath or camel.management.authenticationPath properties. Check if these are explicitly set to a specific path.
    Affected if These properties are either not set or are set to an exact path rather than a path with wildcard/subpath matching.

You are affected if you run a vulnerable Camel version (4.14.1-4.14.5, 4.15.0-4.18.1) with authentication enabled and a non-root context path, and the management endpoint /admin/observe/info (or similar) is accessible without credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.6 / 4.18.2 or later
Fixed in 4.14.64.18.2
Interim mitigation

Upgrade Apache Camel to version 4.14.6, 4.18.2, or 4.20.0 which contains the fix for proper subpath authentication matching.

Recommended fix High confidence

4.20.0 (or 4.14.6 for 4.14.x LTS, or 4.18.2 for 4.18.x LTS)

  1. 1. Identify the current Apache Camel version in use by checking your project dependencies (e.g., pom.xml, build.gradle)
  2. 2. Determine which LTS stream you are on: 4.14.x or 4.18.x
  3. 3. For 4.14.x LTS users: upgrade Apache Camel to version 4.14.6
  4. 4. For 4.18.x LTS users: upgrade Apache Camel to version 4.18.2
  5. 5. Alternatively, upgrade to the latest stable version 4.20.0 which contains the fix
  6. 6. After upgrading, verify that authentication is correctly enforced on all subpaths under the configured context path
  7. 7. Test that unauthenticated requests to subpaths (e.g., /api/route, /admin/observe/info) are now properly challenged for credentials

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40022 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data