CVE-2026-80312: Apache Camel: Camel-OAuth Authentication Bypass via Fail-Open Processors

Published Oct 19, 2026
·
Updated

Improper Authentication vulnerability in Apache Camel OAuth component.

This issue affects Apache Camel: from 4.11.0 before 4.18.5, from 4.19.0 before 4.22.1.

The camel-oauth processors that guard a route did not stop the exchange when authentication could not be completed. Where a failure to establish an authenticated session should have terminated routing and returned an error to the caller, the processors fell through and returned control to the route, so the request continued to the protected endpoint as though authentication had succeeded. The effect is a fail-open authentication guard: an unauthenticated caller reached whatever the route did next. The condition is reached on the ordinary request path of a route configured to require OAuth, and needs no special configuration or prior access on the caller's part.

Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The processors now stop the exchange and set the appropriate error status whenever an authenticated session cannot be established, so a failed authentication no longer reaches the protected part of the route. For deployments that cannot upgrade immediately, place an explicit authorization check after the OAuth processor rather than relying on it to halt the exchange, and verify that the route stops on failure.

Affected Software

1 affected component
Apache Camel>=4.11.0<4.18.5, >=4.19.0<4.22.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.23.0
  2. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.18.5
  3. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.22.1
  4. Compensating control

    For deployments that cannot upgrade immediately, place an explicit authorization check after the OAuth processor and verify that the route stops on authentication failure before reaching the protected endpoint.

Event History

Oct 19, 2026
CVE Published
via MITRE·10:27 AM
Data Sourced
via MITRE·10:27 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·11:17 AM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203