Severity:
CVSS 3.1: 8.2 (high) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-oauth) 4.11.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-oauth) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-oauth) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-oauth) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-oauth) 4.23.0 unaffected
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.
Solution:
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.
Work Arounds:
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.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-80312.html
https://issues.apache.org/jira/browse/CAMEL-24411
https://github.com/apache/camel/pull/25567
https://github.com/apache/camel/pull/25575
https://github.com/apache/camel/pull/25576
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-80312
