Live › vulnerability › CVE-2026-80312
Go to dashboardThe camel-oauth processors did not stop a request when authentication could not complete, so routing continued to the protected endpoint. An unauthenticated caller can reach whatever the guarded route does next.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications using Apache Camel versions from 4.11.0 before 4.18.5 or from 4.19.0 before 4.22.1 that guard routes with the camel-oauth component. The exposure depends on what sits behind the guarded route, since the request proceeds to it when authentication fails. Teams not using camel-oauth can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-oauth or by reading the camel-oauth version in the build file.4.23.0.4.18.5.4.22.1.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-80312")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.