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

Official description

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 products (as reported)

References

• Apache Camel Security Advisory - CVE-2026-80312 vendor-advisory
• CAMEL-24411 issue-tracking
• Fix on main, released in 4.23.0 (commit a3a98e4c959f3a04d5e5540b60bf2cc36314e37c) patch
• Backport to camel-4.22.x, released in 4.22.1 (commit 2c61e3387ca8a2b811f96eed0520c78e340c2141) patch
• Backport to camel-4.18.x, released in 4.18.5 (commit 407f2829882475648fe5a575810e171dd0d1391d) patch