CVE-2026-80312
8.2HighPublished 19 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-287
Impact
Unauthenticated remote attackers can bypass OAuth checks and access protected backend endpoints. They only need network access to the exposed route.
Root cause
The camel-oauth processor fails open when authentication cannot be completed, letting the exchange fall through to downstream route handlers instead of terminating.
Affected systems
Apache Camel 4.11.0 before 4.18.5, and 4.19.0 before 4.22.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Fix & remediation
Upgrade to Apache Camel 4.23.0, 4.22.1, or 4.18.5. If patching immediately is not possible, add an explicit check directly after the OAuth processor to verify session state and halt the route on failure.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.